Documentation/core-api/atomic_ops.rst

2 Semantics and Behavior of Atomic and Bitmask Operations
28 :ref:`Documentation/core-api/local_ops.rst <local_ops>` for the semantics of
222 memory barrier semantics which satisfy the above requirements, that is
233 semantics are required.
244 Again, these primitives provide explicit memory barrier semantics around
251 provide explicit memory barrier semantics around the operation::
257 This primitive must provide explicit memory barrier semantics around
274 atomic_cmpxchg will only satisfy its atomicity semantics as long as all
281 The semantics for atomic_cmpxchg are the same as those defined for 'cas'
298 If a caller requires memory barrier semantics around an atomic_t
419 With the memory barrier semantics required of the atomic_t operations
443 their SMP and memory barrier semantics are similar in shape and scope
459 semantics required of these interfaces. ::
486 must provide explicit memory barrier semantics around their execution.
512 semantics), two interfaces are provided::
531 There are two special bitops with lock barrier semantics (acquire/release,
533 postfixed variants, except that they are to provide acquire/release semantics,
542 unlock barrier semantics. This can be useful if the lock itself is protecting
560 barrier semantics.
563 memory-barrier semantics as the atomic and bit operations returning