| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ants Aasma <ants(at)cybertec(dot)at>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: better atomics - v0.6 |
| Date: | 2014-09-26 01:08:40 |
| Message-ID: | 20140926010840.GJ16581@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-09-25 21:02:28 -0400, Robert Haas wrote:
> I feel like this could really use a developer README: what primitives
> do we have, which ones are likely to be efficient or inefficient on
> which platforms, how do atomics interact with barriers, etc.
atomics.h has most of that. Including documenting which barrier
semantics the individual operations have. One change I can see as being
a good idea is to move/transform the definition of acquire/release
barriers from s_lock.h to README.barrier.
It doesn't document which operations are efficient on which platform,
but I wouldn't know what to say about that topic? The current set of
operations should be fast on pretty much all platforms.
What information would you like to see? An example of how to use
atomics?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-09-26 01:18:00 | Re: KNN-GiST with recheck |
| Previous Message | Robert Haas | 2014-09-26 01:02:28 | Re: better atomics - v0.6 |