summaryrefslogtreecommitdiffstats
path: root/Documentation/memory-barriers.txt
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2015-02-02 17:08:25 +0100
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2015-02-26 20:57:31 +0100
commitdaf1aab9acfaaded09f53fa91dfe6e4e6926ec39 (patch)
tree4c2206bd517312dfbc4e654a62205cfaf49bb82b /Documentation/memory-barriers.txt
parentdocumentation: Update per-CPU kthreads documentation (diff)
downloadlinux-daf1aab9acfaaded09f53fa91dfe6e4e6926ec39.tar.xz
linux-daf1aab9acfaaded09f53fa91dfe6e4e6926ec39.zip
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>
Diffstat (limited to 'Documentation/memory-barriers.txt')
0 files changed, 0 insertions, 0 deletions