From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: ak@suse.de, dipankar@in.ibm.com, maneesh@in.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Add rcu_assign_pointer() to kill more memory barriers
Date: Tue, 14 Sep 2004 11:40:05 -0700 [thread overview]
Message-ID: <20040914184005.GC1237@us.ibm.com> (raw)
In-Reply-To: <20040914100856.528bd6c9@dell_ss3.pdx.osdl.net>
On Tue, Sep 14, 2004 at 10:08:56AM -0700, Stephen Hemminger wrote:
> Looks good, memory barriers are the second major source of confusion
> for many developers (after locking).
Glad you like it! It passed kernbench on a 4-way x86 box, FYI!
Thanx, Paul
prev parent reply other threads:[~2004-09-14 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 22:30 [RFC][PATCH] Add rcu_assign_pointer() to kill more memory barriers Paul E. McKenney
2004-09-14 17:08 ` Stephen Hemminger
2004-09-14 18:40 ` Paul E. McKenney [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=20040914184005.GC1237@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=ak@suse.de \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=shemminger@osdl.org \
/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