diff options
Diffstat (limited to 'Documentation/memory-barriers.txt')
| -rw-r--r-- | Documentation/memory-barriers.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index 9d5e0f853f08..c239a0cf4b1a 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt | |||
| @@ -498,11 +498,11 @@ And a couple of implicit varieties: | |||
| 498 | This means that ACQUIRE acts as a minimal "acquire" operation and | 498 | This means that ACQUIRE acts as a minimal "acquire" operation and |
| 499 | RELEASE acts as a minimal "release" operation. | 499 | RELEASE acts as a minimal "release" operation. |
| 500 | 500 | ||
| 501 | A subset of the atomic operations described in atomic_ops.txt have ACQUIRE | 501 | A subset of the atomic operations described in core-api/atomic_ops.rst have |
| 502 | and RELEASE variants in addition to fully-ordered and relaxed (no barrier | 502 | ACQUIRE and RELEASE variants in addition to fully-ordered and relaxed (no |
| 503 | semantics) definitions. For compound atomics performing both a load and a | 503 | barrier semantics) definitions. For compound atomics performing both a load |
| 504 | store, ACQUIRE semantics apply only to the load and RELEASE semantics apply | 504 | and a store, ACQUIRE semantics apply only to the load and RELEASE semantics |
| 505 | only to the store portion of the operation. | 505 | apply only to the store portion of the operation. |
| 506 | 506 | ||
| 507 | Memory barriers are only required where there's a possibility of interaction | 507 | Memory barriers are only required where there's a possibility of interaction |
| 508 | between two CPUs or between a CPU and a device. If it can be guaranteed that | 508 | between two CPUs or between a CPU and a device. If it can be guaranteed that |