documentation: Clarify memory-barrier semantics of atomic operations
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 2 Feb 2015 16:08:25 +0000 (08:08 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 26 Feb 2015 19:57:31 +0000 (11:57 -0800)
commitdaf1aab9acfaaded09f53fa91dfe6e4e6926ec39
tree4c2206bd517312dfbc4e654a62205cfaf49bb82b
parentf1360570f420b8b122e7f1cccf456ff7133a3007
documentation: Clarify memory-barrier semantics of atomic operations

All value-returning atomic read-modify-write operations must provide full
memory-barrier semantics on both sides of the operation.  This commit
clarifies the documentation to make it clear that these memory-barrier
semantics are provided by the operations themselves, not by their callers.

Reported-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Documentation/atomic_ops.txt
This page took 0.024116 seconds and 5 git commands to generate.