Re: global barrier & atomics in signal handlers (Re: Atomic operations within spinlocks)
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2020-06-17T18:33:54Z
Lists: pgsql-hackers
Hi, On 2020-06-17 10:34:31 -0400, Robert Haas wrote: > On Tue, Jun 16, 2020 at 3:28 PM Andres Freund <andres@anarazel.de> wrote: > > > I think 0003 looks a little strange: it seems to be > > > testing things that might be implementation details of other things, > > > and I'm not sure that's really correct. In particular: > > Hm? Isn't s_lock the, as its comment says, "platform-independent portion > > of waiting for a spinlock."? I also don't think we need to purely > > follow external APIs in internal tests. > > I feel like we at least didn't use to use that on all platforms, but I > might be misremembering. There's only one definition of S_LOCK, and s_lock is the only spinlock related user of perform_spin_delay(). So I don't think so? > It seems odd and confusing that we have both > S_LOCK() and s_lock(), anyway. Differentiating functions based on case > is not great practice. It's a terrible idea, yes. Since we don't actually have any non-default implementations of S_LOCK, perhaps we should just rip it out? It'd probably be clearer if SpinLockAcquire() would be what uses TAS() and falls back to s_lock (best renamed to s_lock_slowpath or such). It'd perhaps also be good to make SpinLockAcquire() a static inline instead of a #define, so it can be properly attributed in debuggers and profilers. Greetings, Andres Freund
Commits
-
Convert SpinLock* macros to static inline functions.
- bfc321b4723e 19 (unreleased) landed
-
Clean up includes of s_lock.h.
- f219167910ad 14.0 landed
-
Fix deadlock danger when atomic ops are done under spinlock.
- 5fffa8fce37b 13.0 landed
- 6cc2866c4cdf 12.4 landed
- 825d89dda5ad 11.9 landed
- c2a84bee1228 10.14 landed
- 8bc13287ed3e 9.6.19 landed
- 3e69bf3b142b 9.5.23 landed
- cf1234a10e50 14.0 landed
-
Add basic spinlock tests to regression tests.
- 3f66e1c5a576 10.14 landed
- e027219f2131 11.9 landed
- 008c119928a3 12.4 landed
- 59225dcefef2 13.0 landed
- 3b37a6de027c 14.0 landed
- e8302f107af9 9.6.19 landed
- 7e91f90a8ed4 9.5.23 landed
-
spinlock emulation: Fix bug when more than INT_MAX spinlocks are initialized.
- dcf3cb60cbef 9.5.23 landed
- 660622053419 9.6.19 landed
- b295f666b7f0 10.14 landed
- 34d29222a0bb 11.9 landed
- b91cfaa34f44 12.4 landed
- 276bdc93924a 13.0 landed
- 4d4ca24efe8e 14.0 landed
-
Avoid potential spinlock in a signal handler as part of global barriers.
- 09bff91b316e 13.0 landed
- fd49d5380757 14.0 landed
-
Make pg_stat_wal_receiver consistent with the WAL receiver's shmem info
- 2c8dd05d6cbc 13.0 cited
-
Improve 64bit atomics support.
- e8fdbd58fe56 10.0 cited