Postgres Pro
Downloads
Home   >   mailing lists

Re: Spinlocks and compiler/memory barriers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Spinlocks and compiler/memory barriers
Date
Msg-id 60825.1403817187@sss.pgh.pa.us
Whole thread Raw
In response to Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Tree view 
Andres Freund <andres@2ndquadrant.com> writes:
> I think we should rework things so that we fall back to
> pg_write_barrier(), (*((volatile slock_t *) (lock)) = 0) instead of what
> we have right now.

Surely it had better be a read barrier as well?  And S_LOCK the same?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Spinlocks and compiler/memory barriers
Next
From: Jeff Janes
Date:
Subject: Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]