[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0609111246110.10623-100000@iolanthe.rowland.org>
Date: Mon, 11 Sep 2006 12:50:07 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: "Paul E. McKenney" <paulmck@...ibm.com>
cc: Oliver Neukum <oliver@...kum.org>,
David Howells <dhowells@...hat.com>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Uses for memory barriers
On Mon, 11 Sep 2006, Paul E. McKenney wrote:
> This is a summary of the Linux memory-barrier semantics as I understand
> them:
>
> 1. A given CPU will always perceive its own memory operations
> as occuring in program order.
>
> 2. All stores to a given single memory location will be perceived
> as having occurred in the same order by all CPUs. This is
> "coherence". (And this is the property that I was forgetting
> about when I first looked at your second example.)
...
This can't be right. Together 1 and 2 would obviate the need for wmb().
The CPU doing "STORE A; STORE B" will always see the operations occuring
in program order by 1, and hence every other CPU would always see them
occurring in the same order by 2 -- even without wmb().
Either 2 is too strong, or else what you mean by "perceived" isn't
sufficiently clear.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists