lkml.org 
[lkml]   [2004]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86 bitops.h commentary on instruction reordering
On Fri, Aug 06, 2004 at 07:36:25PM +0400, Vladislav Bolkhovitin wrote:
> Thanks.
>
> One more question, if you don't object. How after some variable
> assigment to make other CPUs *immediatelly* see the assigned value, i.e.
> to make current CPU immediately flush its write cache in memory? *mb()
> seems deal with reordering, barrier() with the compiler optimization (am
> I right?).

Yes correct. *mb() usually imply barrier().

About the flush, each architecture defines its own instruction for doing so,
PowerPC has "sync" and "isync" instructions (to flush the whole cache and instruction
cache respectively), MIPS has "sync" and so on..

> The similar memory barrier spin_lock() does, but it's not
> easy to uderstand its internal magic.

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.062 / U:4.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site