From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Spinlocks and compiler/memory barriers |
Date: | 2014-09-04 12:18:37 |
Message-ID: | CA+TgmoYBN7cAmng-pWt_C+joVS-dfjZRY7+dUbpzWp0AqZ0OQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 5, 2014 at 11:55 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Jul 6, 2014 at 3:12 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>>> > If you want to do that, it's fine with me. What I would do is:
>>> >
>>> > - Back-patch the addition of the sparcv8+ stuff all the way. If
>>> > anyone's running anything older, let them complain...
>>> > - Remove the special case for MIPS without gcc intrinsics only in
>>> > master, leaving the back-branches broken. If anyone cares, let them
>>> > complain...
>>> > - Nothing else.
>>>
>>> I've gone ahead and done the second of these things.
>>
>> Thanks.
>>
>>> Andres, do you want to go take a stab at fixing the SPARC stuff?
>>
>> Will do, will probably take me till thursday to come up with the brain
>> cycles.
>
> Ping?
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-09-04 12:19:47 | Re: Spinlocks and compiler/memory barriers |
Previous Message | Robert Haas | 2014-09-04 12:16:55 | Re: Scaling shared buffer eviction |