| commit | daf1aab9acfaaded09f53fa91dfe6e4e6926ec39 | [log] [tgz] |
|---|---|---|
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | Mon Feb 02 08:08:25 2015 -0800 |
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | Thu Feb 26 11:57:31 2015 -0800 |
| tree | 4c2206bd517312dfbc4e654a62205cfaf49bb82b | |
| parent | f1360570f420b8b122e7f1cccf456ff7133a3007 [diff] |
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>