diff options
| author | David Howells <dhowells@redhat.com> | 2006-04-10 22:54:23 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-04-11 06:18:44 -0700 |
| commit | dbc8700e27a94621de9d22c506c67913e0121501 (patch) | |
| tree | 4ac767de021735f8826ac849ac8a3795bd78ade5 /Documentation/feature-removal-schedule.txt | |
| parent | 235963b2edc080b577000031b9ad75804dd83c88 (diff) | |
| download | kernel-crypto-dbc8700e27a94621de9d22c506c67913e0121501.tar.gz kernel-crypto-dbc8700e27a94621de9d22c506c67913e0121501.tar.xz kernel-crypto-dbc8700e27a94621de9d22c506c67913e0121501.zip | |
[PATCH] Fix memory barrier docs wrt atomic ops
Fix the memory barrier documentation to attempt to describe atomic ops
correctly.
atomic_t ops that return a value _do_ imply smp_mb() either side, and so
don't actually require smp_mb__*_atomic_*() special barriers.
Also explains why special barriers exist in addition to normal barriers.
Further fix the memory barrier documents to portray bitwise operation
memory barrier effects correctly following Nick Piggin's comments.
It makes the point that any atomic op that both modifies some state in
memory and returns information on that state implies memory barriers on
both sides.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
0 files changed, 0 insertions, 0 deletions