projects/linux·commit 75b2bd55

[PATCH] A minor fix for set_mb() in Documentation/memory-barriers.txt

75b2bd55 · Oleg Nesterov <[email protected]> · 2006-11-08 17:44:38 -08:00

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 <[email protected]>
Acked-by: David Howells <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Commit
75b2bd55bd7724c727856fbdf3ab71d2e4287ac8
Parents
d654c673

Changes

1 files changed · +1 −1

FileStatusAddDelContent
Documentation/memory-barriers.txtmodified+1−1View file

Documentation/memory-barriers.txt

View file
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 7f790f6..7751704 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.