Re: why roll-your-own s_lock? / improving scalability - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why roll-your-own s_lock? / improving scalability
Date
Msg-id 14481.1340748739@sss.pgh.pa.us
Whole thread Raw
In response to Re: why roll-your-own s_lock? / improving scalability  (Martijn van Oosterhout <kleptog@svana.org>)
Responses experimental: replace s_lock spinlock code with pthread_mutex on linux  (Nils Goroll <slink@schokola.de>)
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> And then you have fabulous things like:
> https://git.reviewboard.kde.org/r/102145/
> (OSX defines _POSIX_THREAD_PROCESS_SHARED but does not actually support
> it.)

> Seems not very well tested in any case.

> It might be worthwhile testing futexes on Linux though, they are
> specifically supported on any kind of shared memory (shm/mmap/fork/etc)
> and quite well tested.

Yeah, a Linux-specific replacement of spinlocks with futexes seems like
a lot safer idea than "let's rely on posix mutexes everywhere".  It's
still unproven whether it'd be an improvement, but you could expect to
prove it one way or the other with a well-defined amount of testing.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Catalog/Metadata consistency during changeset extraction from wal
Next
From: Daniel Farina
Date:
Subject: Re: Posix Shared Mem patch