From ee737c074553f1be1f78c1981c5f4ddafe47ee31 Mon Sep 17 00:00:00 2001 From: Oleg Nesterov Date: Wed, 8 Nov 2006 17:44:38 -0800 Subject: [PATCH] --- yaml --- r: 40816 b: refs/heads/master c: 75b2bd55bd7724c727856fbdf3ab71d2e4287ac8 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/memory-barriers.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 9c4bdc5ec218..d9cd9e20210a 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: d654c673d6394bc26e159b1057b357371b4ce1dc +refs/heads/master: 75b2bd55bd7724c727856fbdf3ab71d2e4287ac8 diff --git a/trunk/Documentation/memory-barriers.txt b/trunk/Documentation/memory-barriers.txt index 7f790f66ec68..7751704b6db1 100644 --- a/trunk/Documentation/memory-barriers.txt +++ b/trunk/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.