From 806ced8ced09937f1c363773a3720cbc1641a245 Mon Sep 17 00:00:00 2001 From: Steven Rostedt Date: Fri, 14 Jul 2006 16:05:01 -0400 Subject: [PATCH] --- yaml --- r: 32676 b: refs/heads/master c: f92213bae062cf88c099fbfd3040fef512b19905 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/memory-barriers.txt | 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index 9dc8b3c877dc..bb9f5171efec 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: bb129994c3bff9c5e8df91f05d7e9b6402fbd83f +refs/heads/master: f92213bae062cf88c099fbfd3040fef512b19905 diff --git a/trunk/Documentation/memory-barriers.txt b/trunk/Documentation/memory-barriers.txt index 28d1bc3edb1c..46b9b389df35 100644 --- a/trunk/Documentation/memory-barriers.txt +++ b/trunk/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.