diff options
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-02-02 08:08:25 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-02-26 11:57:31 -0800 |
| commit | daf1aab9acfaaded09f53fa91dfe6e4e6926ec39 (patch) | |
| tree | 4c2206bd517312dfbc4e654a62205cfaf49bb82b /Documentation/memory-barriers.txt | |
| parent | f1360570f420b8b122e7f1cccf456ff7133a3007 (diff) | |
| download | linux-0-day-daf1aab9acfaaded09f53fa91dfe6e4e6926ec39.tar.gz linux-0-day-daf1aab9acfaaded09f53fa91dfe6e4e6926ec39.tar.xz | |
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