Linux Headquarters
[ Register ]
[ About us ] [ Home Page ]

Advertisement
[ Kernel ] [ Documentation ] [ Links ] [ Books ]

Advertisement

Kernel v2.4.19 /Documentation/DocBook/kernel-locking.tmpl

Filename:/Documentation/DocBook/kernel-locking.tmpl
Lines Added:12
Lines Deleted:2
Also changed in: (Previous) 2.4.19-rc5  2.4.19-rc4  2.4.19-rc3  2.4.19-rc2  2.4.19-rc1  2.4.19-pre10 
(Following) 2.4.21-pre2  2.4.21-pre3  2.4.21-pre4  2.4.21-pre5  2.4.21-pre6  2.4.21-pre7 

Location
[  2.4.19
  [  Documentation
    [  DocBook
       o  kernel-locking.tmpl

Patch

diff -urN linux-2.4.18/Documentation/DocBook/kernel-locking.tmpl linux-2.4.19/Documentation/DocBook/kernel-locking.tmpl
--- linux-2.4.18/Documentation/DocBook/kernel-locking.tmpl   Sat May 19 17:43:05 2001
+++ linux-2.4.19/Documentation/DocBook/kernel-locking.tmpl   Fri Aug  2 17:39:42 2002
@@ -788,8 +788,18 @@
     </para>
 
     <para>
-      Note that the atomic operations are defined to act as both
-      read and write barriers on all platforms.
+      Note that the atomic operations do in general not act as memory
+      barriers. Instead you can insert a memory barrier before or
+      after <function>atomic_inc()</function> or
+      <function>atomic_dec()</function> by inserting
+      <function>smp_mb__before_atomic_inc()</function>,
+      <function>smp_mb__after_atomic_inc()</function>,
+      <function>smp_mb__before_atomic_dec()</function> or
+      <function>smp_mb__after_atomic_dec()</function>
+      respectively. The advantage of using those macros instead of
+      <function>smp_mb()</function> is, that they are cheaper on some
+      platforms.    
+      <!-- Sebastian Wilhelmi <seppi@seppi.de> 2002-03-04 -->
     </para>
    </sect1>
 


Comments: webmaster (at) linuxhq.com.
Advertising: banners (at) linuxhq.com.
Compilation ©1998-2008 Linux Headquarters, Inc.