path: root/Documentation/memory-barriers.txt
diff options
authorOleg Nesterov <oleg@tv-sign.ru>2006-11-08 17:44:38 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-11-08 18:29:22 -0800
commit75b2bd55bd7724c727856fbdf3ab71d2e4287ac8 (patch)
tree45bf6e8091f1b932cee4a499f46c9ef17fb9a2d8 /Documentation/memory-barriers.txt
parentd654c673d6394bc26e159b1057b357371b4ce1dc (diff)
[PATCH] A minor fix for set_mb() in Documentation/memory-barriers.txt
set_mb() is used by set_current_state() which needs mb(), not wmb(). I think it would be right to assume that set_mb() implies mb(), all arches seem to do just this. Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru> Acked-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/memory-barriers.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 7f790f66ec6..7751704b6db 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1016,7 +1016,7 @@ There are some more advanced barrier functions:
(*) set_mb(var, value)
- This assigns the value to the variable and then inserts at least a write
+ This assigns the value to the variable and then inserts a full memory
barrier after it, depending on the function. It isn't guaranteed to
insert anything more than a compiler barrier in a UP compilation.