aboutsummaryrefslogtreecommitdiff
path: root/Documentation/memory-barriers.txt
diff options
context:
space:
mode:
authorSteven Rostedt <rostedt@goodmis.org>2006-07-14 16:05:01 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2006-07-14 21:56:14 -0700
commitf92213bae062cf88c099fbfd3040fef512b19905 (patch)
treed4bc2ba0cae7dbad57ccc3e6bfe166db82ee2896 /Documentation/memory-barriers.txt
parentbb129994c3bff9c5e8df91f05d7e9b6402fbd83f (diff)
[PATCH] remove set_wmb - doc update
This patch removes the reference to set_wmb from memory-barriers.txt since it shouldn't be used. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/memory-barriers.txt')
-rw-r--r--Documentation/memory-barriers.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 28d1bc3edb1..46b9b389df3 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1015,10 +1015,9 @@ CPU from reordering them.
There are some more advanced barrier functions:
(*) set_mb(var, value)
- (*) set_wmb(var, value)
- These assign the value to the variable and then insert at least a write
- barrier after it, depending on the function. They aren't guaranteed to
+ This assigns the value to the variable and then inserts at least a write
+ barrier after it, depending on the function. It isn't guaranteed to
insert anything more than a compiler barrier in a UP compilation.