diff options
| author | Ivan Maidanski <ivmai@mail.ru> | 2013-01-15 00:56:35 +0400 |
|---|---|---|
| committer | Ivan Maidanski <ivmai@mail.ru> | 2013-02-02 14:05:18 +0400 |
| commit | 6e1617b18edb999810c3448c55867bcb00f9c881 (patch) | |
| tree | 13bb496cebf60c1f6bb77bd5449925a8fef0221a | |
| parent | e235d95d43b2b64d5f9b7fcd9ed85e07a88e5f20 (diff) | |
Fix README regarding _acquire_read barrier
* doc/README.txt (_acquire_read): Add information about memory
barrier (similar as in atomic_ops.h).
* doc/README.txt (_release_read): Remove information about
non-existing barrier.
| -rw-r--r-- | doc/README.txt | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/README.txt b/doc/README.txt index 88445c0..7f7959e 100644 --- a/doc/README.txt +++ b/doc/README.txt @@ -159,6 +159,8 @@ _full: Ordered with respect to both earlier and later memory ops. _release_write: Ordered with respect to earlier writes. This is normally implemented as either a _write or _release barrier. +_acquire_read: Ordered with respect to later reads. This is + normally implemented as either a _read or _acquire barrier. _dd_acquire_read: Ordered with respect to later reads that are data dependent on this one. This is needed on a pointer read, which is later dereferenced to read a @@ -170,10 +172,6 @@ _dd_acquire_read: Ordered with respect to later reads that are data eliminate dependencies from the generated code, since dependencies force the hardware to execute the code serially.) -_release_read: Ordered with respect to earlier reads. Useful for - implementing read locks. Can be implemented as _release, - but not as _read, since _read groups the current operation - with the earlier ones. We assume that if a store is data-dependent on an a previous load, then the two are always implicitly ordered. |