From: Darren Hart <dvhart@infradead.org>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
dave@stgolabs.net, Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
linux@rasmusvillemoes.dk, dvhart@linux.intel.com,
bigeasy@linutronix.de, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH v2] futex: replace bare barrier() with a READ_ONCE()
Date: Wed, 2 Mar 2016 08:41:21 -0800 [thread overview]
Message-ID: <20160302164121.GA1092@dvhart-mobl5.amr.corp.intel.com> (raw)
In-Reply-To: <CAHz2CGX=uh6rvKVyZ21dA95v9wcpBC=8Ldv-3Yjhk6Z3iNtBJw@mail.gmail.com>
On Wed, Mar 02, 2016 at 09:56:32PM +0800, Jianyu Zhan wrote:
> On Wed, Mar 2, 2016 at 9:35 PM, Christian Borntraeger
> <borntraeger@de.ibm.com> wrote:
> > That change makes sense. I did the original barrier back in 2006 (could you cc me next time?)
>
> Sorry for that, I thought get_maintainer.pl would had spit the
> original author's email, but apparently it didn't :(
get_maintainer gives you the documented maintainers per the MAINTAINERS file, as
well as frequent committers. This patch was in 2008. Always include the author
of patches you are referencing (and that's manual).
>
> > ACCESS_ONCE or READ_ONCE was not available at that time and its now the better way.
> >
Noting this specifically in the commit message helps the argument and why the
change is being made now.
> > This is not an s390 specific problem, it was just triggered there as the gcc cost model
> > considered the memory read as cheap as a register read.
> >
>
> Thanks for the clarification.
>
And as with the original patch (e91467ecd1ef), we should be able to justify the
change with an assembly dump, as Christian did in his commit.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-03-02 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 13:08 Jianyu Zhan
2016-03-02 13:35 ` Christian Borntraeger
2016-03-02 13:56 ` Jianyu Zhan
2016-03-02 16:41 ` Darren Hart [this message]
2016-03-02 16:48 ` Darren Hart
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=20160302164121.GA1092@dvhart-mobl5.amr.corp.intel.com \
--to=dvhart@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=borntraeger@de.ibm.com \
--cc=dave@stgolabs.net \
--cc=dvhart@linux.intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@kernel.org \
--cc=nasa4836@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®