Re: [PATCH] Document Linux's memory barriers [try #4]

[Nick Piggin <nickpiggin@yahoo.com.au>]

David Howells wrote:

> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>
> > > Ah, but if the cache is on the CPU side of the dotted line, does that then
> > > mean that a write memory barrier guarantees the CPU's cache to have
> > > updated memory?
> > I don't think it has to[*]. It would guarantee the _order_ in which "global
> > memory" of this model ie. visibility for other "CPUs" see the writes,
> > whether that visibility ultimately be implemented by cache coherency
> > protocol or something else, I don't think matters (for a discussion of
> > memory ordering).
>
> It does matter, because I have to make it clear that the effect of the memory
> barrier usually stops at the cache, and in fact memory barriers may have no
> visibility at all on another CPU because it's all done inside a CPU's cache,
> until that other CPU tries to observe the results.

But that's a cache coherency issue that is really orthogonal to the memory
consistency one. WHY, when explaining memory consistency, do they need to
know that a barrier "usually stops at cache" (except for alpha)?

They already _know_ that barriers may have no visibility on any other CPU
because you should tell them that barriers only imply an ordering over the
horizon, nothing more (ie. they need not imply a "push").

> > If anything it confused the matter for the case of Alpha.
>
> Nah... Alpha is self-confusing:-)

Well maybe ;) But for better or worse, it is what kernel programmers now 
have to
deal with.

> > All the programmer needs to know is that there is some horizon (memory)
> > beyond which stores are visible to other CPUs, and stores can travel there
> > at different speeds so later ones can overtake earlier ones. And likewise
> > loads can come from memory to the CPU at different speeds too, so later
> > loads can contain earlier results.
>
> They also need to know that memory barriers don't imply an ordering on the
> cache.

Why? I'm contending that this is exactly what they don't need to know.

> > [*] Nor would your model require a smp_wmb() to update CPU caches either, I
> > think: it wouldn't have to flush the store buffer, just order it.
>
> Exactly.
>
> But in your diagram, given that it doesn't show the cache, you don't know that
> the memory barrier doesn't extend through the cache and all the way to memory.

What do you mean "extend"? I don't think that is good terminology. What 
it does is
provide an ordering of traffic going over the vertical line dividing CPU 
and memory.
It does not matter whether "memory" is actually "cache + coherency" or 
not, just
that the vertical line is the horizon between "visible to other CPUs" 
and "not".

Nick
--

Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/