From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Documentation/memory-barriers.txt
Date: Mon, 12 Sep 2011 19:56:05 -0400 [thread overview]
Message-ID: <20110912235605.GA12886@synalogic.ca> (raw)
In-Reply-To: <20110912163307.GC2362@linux.vnet.ibm.com>
On 11-09-12 09:33, Paul E. McKenney wrote:
> On Mon, Sep 12, 2011 at 10:15:20AM -0400, Benjamin Poirier wrote:
> > Hello David, Paul,
> >
[snip]
>
> This example would be correct for a looping case, but is more ornate than
> required for illustrating the effects of memory barriers. So we took the
> simpler case without the loop.
Thanks for the clarification. I was under the false impression that all
of the code examples in this section represented the same code segment
that was modified from one example to the next. In any case, these
examples do demonstrate the use of memory barriers clearly.
-Ben
prev parent reply other threads:[~2011-09-12 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 14:15 Documentation/memory-barriers.txt Benjamin Poirier
2011-09-12 16:33 ` Documentation/memory-barriers.txt Paul E. McKenney
2011-09-12 23:56 ` Benjamin Poirier [this message]
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=20110912235605.GA12886@synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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