public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@osdl.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hugh@veritas.com>,
	Jan Beulich <jbeulich@novell.com>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	Pratap Subrahmanyam <pratap@vmware.com>
Subject: Re: [PATCH 2/2] I386 convert pae wmb to non smp
Date: Thu, 27 Apr 2006 13:30:29 +1000	[thread overview]
Message-ID: <44503AD5.9020605@yahoo.com.au> (raw)
In-Reply-To: <445019E7.80900@vmware.com>

Zachary Amsden wrote:

> Nick Piggin wrote:
>
>> wmb() means that it also orders IO memory. It is no difference for
>> i386, but smp_wmb() actually has the right semantics of the abstract
>> Linux memory model.
>
>
> The name is pretty confused.  smp_wmb seems to imply an SMP-only 
> barrier, whereas we want here a write barrier on regular memory.


That is just a compiler barrier (barrier()). A CPU should always be 
consistent with
itself so memory ordering doesn't really apply there (hence smp_ prefix, 
which also
are compiler barriers, of course).

>   Both smp_wmb and wmb() are identical in that they both reduce to 
> barrier today, but I confess not to know which one semantically is 
> correct.


Well you're only looking at i386. True it is i386 specific code, but 
sticking
to the Linux memory model is more clear and consistent I think.

>   Your call on this patch - it is unecessary, I thought it was more 
> semantically correct, but you probably know that better than me.  So, 
> drop part 2 of this patch?


Yes, and make part 1 use smp_wmb.

--

Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-27  3:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 22:03 [PATCH 2/2] I386 convert pae wmb to non smp Zachary Amsden
2006-04-27  0:00 ` Nick Piggin
2006-04-27  1:09   ` Zachary Amsden
2006-04-27  3:30     ` Nick Piggin [this message]
2006-04-27  8:21       ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44503AD5.9020605@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=akpm@osdl.com \
    --cc=hugh@veritas.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap@vmware.com \
    --cc=zach@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox