Each operation name also includes a suffix that specifies the associated
ordering semantics. The ordering constraint limits reordering of this
-operation with repsect to other atomic operations and ordinary memory
+operation with respect to other atomic operations and ordinary memory
references. The current implementation assumes that all memory references
are to ordinary cacheable memory; the ordering guarantee is with respect
to other threads or processes, not I/O devices. (Whether or not this
the atomic operation or preceding it. Rarely useful for clients?
_write: Earlier writes become visible before writes during or after
the atomic operation. Rarely useful for clients?
-_full: Ordered with respect to both earlier and later memops.
+_full: Ordered with respect to both earlier and later memory ops.
AO_store_full or AO_nop_full are the normal ways to force a store
to be ordered with respect to a later load.
_release_write: Ordered with respect to earlier writes. This is