Atomics hardware support table & supported architectures

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Atomics hardware support table & supported architectures
Date: 2014-06-15 01:12:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


At this year developer's meeting we'd discussed the atomics abstraction
which is necessary for some future improvements. We'd concluded that a
overview over the hardware capabilities of the supported platforms would
be helpful. I've started with that at:

Does somebody want other columns in there?

From that and previous discussions
) I think we should definitely remove some platforms:
1) VAX. Production ceased 1997. We've never supported OpenVMS, just
netbsd (and probably openbsd)
2) m32r. Our implementation depends on an *unmerged* glibc header. The
website was dead for several *years*, even after the restore patches
can't be downloaded anymore (404).
3) sparcv8: Last released model 1997.
4) i386: Support dropped from windows 98 (yes, really), linux, openbsd
(yes, really), netbsd (yes, really). No code changes needed.
5) pa-risc.
6) armv-v5
Note that this is *not* a requirement for the atomics abstraction - it
now has a fallback to spinlocks if atomics aren't available. But I don't
think we should add code for practically irrelevant and likely not
working setups.

That'd get us to the situation that all supported platforms support
atomic add & cmpxchg.

Just as a recap: The reason I want the atomics abstraction is so we can
implement improvements like
and quite a few others sanely.


Andres Freund

Andres Freund
PostgreSQL Development, 24x7 Support, Training & Services


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-06-15 02:34:04 Re: Minmax indexes
Previous Message Jim Nasby 2014-06-15 00:44:03 Re: Add CREATE support to event triggers