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

From Robert Haas
Subject Re: Spinlocks and compiler/memory barriers
Date
Msg-id CA+TgmoY9_gFyr0r9M405QTxkgqv07Yv-hwGy+q_hfgdn10S5CA@mail.gmail.com
Whole thread Raw
In response to Re: Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Spinlocks and compiler/memory barriers
List pgsql-hackers
On Mon, Sep 8, 2014 at 7:10 PM, Andres Freund <andres@2ndquadrant.com> wrote:
>> This has been pending for almost two months now and, at your request,
>> my patch to make spinlocks act as compiler barriers is waiting behind
>> it.  Can we please get this moving again soon, or can I commit that
>> patch and you can fix this when you get around to it?
>
> I finally pushed this. And once more I seriously got pissed at the poor
> overall worldwide state of documentation and continously changing
> terminology around this.

There does seem to be a deficit in that area.

> Sorry for taking this long :(
>
> Do you have a current version of your patch to make them compiler
> barriers?

I had forgotten that it needed an update.  Thanks for the reminder.  Here's v2.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: pg_background (and more parallelism infrastructure patches)
Next
From: Robert Haas
Date:
Subject: Re: posix_fadvise() and pg_receivexlog