Re: Spinlocks and compiler/memory barriers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Spinlocks and compiler/memory barriers
Date: 2014-07-01 20:54:35
Message-ID: 20734.1404248075@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Despite my concerns about keeping the list of supported atomics short,
> and I do have concerns in that area, I'm not really sure that we have
> much choice but to go in that direction. We can't accept a >5x
> performance hit in the name of portability, and that's literally what
> we're talking about in some cases. I definitely want to think
> carefully about how we proceed in this area but doing nothing doesn't
> seem like an option.

To be clear, I'm not advocating doing nothing (and I don't think anyone
else is). It's obvious based on Andres' results that we want to use
atomics on platforms where they're well-supported. The argument is
around what we're going to do for other platforms.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2014-07-01 20:58:53 Re: buildfarm and "rolling release" distros
Previous Message Tom Lane 2014-07-01 20:51:45 Re: /proc/self/oom_adj is deprecated in newer Linux kernels