Re: Memory Barrier Definitions

From: Dave Engebretsen (
Date: Tue May 07 2002 - 16:23:28 EST

Alan Cox wrote:
> > forms of processor memory barrier instructions. It is _very_ expensive
> I think I follow
> You have
> Compiler ordering
> CPU v CPU memory ordering
> CPU v I/O memory ordering
> I/O v I/O memory ordering

Yep, that is a good summary. And the problem arises from the very large
penalty for the syncronization form used for CPU v I/O ordering. You
only want to pay that when necessary, certainly not when only CPU v CPU
ordering is required. The difference can be on the order of a 1000
cycles (depending on many factors, of course).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:31 EST