diff options
author | Alexey Dobriyan <adobriyan@gmail.com> | 2014-06-06 14:36:41 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-06-06 16:08:11 -0700 |
commit | 615cc2c9cf9529846fbc342560d6787c2ccaaeea (patch) | |
tree | 06c165479bc9ef613c0b74fd50ac88346dd91c60 /kernel/fork.c | |
parent | 0b07cb8271507ca99cca79222a1dc92ba415f06b (diff) | |
download | op-kernel-dev-615cc2c9cf9529846fbc342560d6787c2ccaaeea.zip op-kernel-dev-615cc2c9cf9529846fbc342560d6787c2ccaaeea.tar.gz |
Documentation/memory-barriers.txt: fix important typo re memory barriers
Examples introducing neccesity of RMB+WMP pair reads as
A=3 READ B
www rrrrrr
B=4 READ A
Note the opposite order of reads vs writes.
But the first example without barriers reads as
A=3 READ A
B=4 READ B
There are 4 outcomes in the first example.
But if someone new to the concept tries to insert barriers like this:
A=3 READ A
www rrrrrr
B=4 READ B
he will still get all 4 possible outcomes, because "READ A" is first.
All this can be utterly confusing because barrier pair seems to be
superfluous. In short, fixup first example to match latter examples
with barriers.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions