瀏覽代碼

[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>
Oleg Nesterov 18 年之前
父節點
當前提交
75b2bd55bd
共有 1 個文件被更改,包括 1 次插入1 次删除
  1. 1 1
      Documentation/memory-barriers.txt

+ 1 - 1
Documentation/memory-barriers.txt

@@ -1016,7 +1016,7 @@ There are some more advanced barrier functions:
 
 
  (*) set_mb(var, value)
  (*) 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
      barrier after it, depending on the function.  It isn't guaranteed to
      insert anything more than a compiler barrier in a UP compilation.
      insert anything more than a compiler barrier in a UP compilation.