pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: neilc@samurai.com
Cc: markw@osdl.org
Cc: pgsql-performance@postgresql.org
Subject: Re: futex results with dbt-3
Date: Wed, 20 Oct 2004 18:51:49 +0200
Message-ID: <417697A5.1050600@colorfullife.com> (raw)
In-Reply-To: <20151.1098222733@sss.pgh.pa.us>
References: <417221B5.1050704@colorfullife.com>
	<20151.1098222733@sss.pgh.pa.us>

Tom Lane wrote:

>Manfred Spraul <manfred@colorfullife.com> writes:
>  
>
>>Has anyone tried to replace the whole lwlock implementation with 
>>pthread_rwlock? At least for Linux with recent glibcs, pthread_rwlock is 
>>implemented with futexes, i.e. we would get a fast lock handling without 
>>os specific hacks.
>>    
>>
>
>"At least for Linux" does not strike me as equivalent to "without
>OS-specific hacks".
>
>  
>
For me, "at least for Linux" means that I have tested the patch with 
Linux. I'd expect that the patch works on most recent unices 
(pthread_rwlock_t is probably mandatory for Unix98 compatibility). You 
and others on this mailing list have access to other systems - my patch 
should be seen as a call for testers, not as a proposal for merging. I 
expect that Linux is not the only OS with fast user space semaphores, 
and if an OS has such objects, then the pthread_ locking functions are 
hopefully implemented by using them. IMHO it's better to support the 
standard function instead of trying to use the native (and OS specific) 
fast semaphore functions.

>The bigger problem here is that the SMP locking bottlenecks we are
>currently seeing are *hardware* issues (AFAICT anyway).  The only way
>that futexes can offer a performance win is if they have a smarter way
>of executing the basic atomic-test-and-set sequence than we do;
>  
>
lwlocks operations are not a basic atomic-test-and-set sequence. They 
are spinlock, several nonatomic operations, spin_unlock.

--
    Manfred



view thread (24+ messages)  latest in thread

Message-ID: <417697A5.1050600@colorfullife.com>
Permalink:  ../417697A5.1050600@colorfullife.com/
Also on:    postgresql.org/message-id/417697A5.1050600@colorfullife.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: manfred@colorfullife.com, tgl@sss.pgh.pa.us, neilc@samurai.com, markw@osdl.org
  Subject: Re: futex results with dbt-3
  In-Reply-To: <417697A5.1050600@colorfullife.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox