[PATCH] kernel locking guide fix.

From: Rusty Russell (rusty@rustcorp.com.au)
Date: Wed May 02 2001 - 06:15:53 EST


diff -urN -I \$.*\$ -X /tmp/kerndiff.hKrYxB --minimal linux-2.4.4-official/Documentation/DocBook/kernel-locking.tmpl working-2.4.4-rcu/Documentation/DocBook/kernel-locking.tmpl
--- linux-2.4.4-official/Documentation/DocBook/kernel-locking.tmpl Tue May 1 12:26:15 2001
+++ working-2.4.4-rcu/Documentation/DocBook/kernel-locking.tmpl Wed May 2 21:14:19 2001
@@ -760,8 +760,11 @@
     </para>
 
     <para>
- Any atomic operation is defined to act as a memory barrier
- (ie. as per the <function>mb()</function> macro). Also,
+ Some atomic operations are defined to act as a memory barrier
+ (ie. as per the <function>mb()</function> macro, but if in
+ doubt, be explicit.
+ <!-- Rusty Russell 2 May 2001, 2.4.4 -->
+ Also,
       spinlock operations act as partial barriers: operations after
       gaining a spinlock will never be moved to precede the
       <function>spin_lock()</function> call, and operations before

--
Premature optmztion is rt of all evl. --DK
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon May 07 2001 - 21:00:12 EST