| commit | 53b926bc22f3983cc780cbed9b3861f767d71b0b | [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> | Mon Feb 02 11:33:41 2015 -0800 |
| tree | 4c9f6c232350fbaa169816d69bf17c7fdbb14c1e | |
| parent | d7a7031a14b6a2039fe6c983da8a82800f07d43a [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>