From: Ingo Molnar <mingo@kernel•org>
To: "Paul E. McKenney" <paulmck@linux•vnet.ibm.com>
Cc: linux-kernel@vger•kernel.org, jiangshanlai@gmail•com,
dipankar@in•ibm.com, akpm@linux-foundation•org,
mathieu.desnoyers@efficios•com, josh@joshtriplett•org,
tglx@linutronix•de, peterz@infradead•org, rostedt@goodmis•org,
dhowells@redhat•com, edumazet@google•com, dvhart@linux•intel.com,
fweisbec@gmail•com, oleg@redhat•com, bobby.prani@gmail•com,
will.deacon@arm•com, boqun.feng@linux•vnet.ibm.com,
linuxppc-dev@lists•ozlabs.org,
Peter Zijlstra <a.p.zijlstra@chello•nl>
Subject: Re: [PATCH tip/core/rcu 2/3] srcu: Force full grace-period ordering
Date: Sun, 15 Jan 2017 10:40:58 +0100 [thread overview]
Message-ID: <20170115094058.GB28621@gmail.com> (raw)
In-Reply-To: <20170115092454.GF5238@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux•vnet.ibm.com> wrote:
> > [sounds of rummaging around in the Git tree]
> >
> > I found this commit of yours from ancient history (more than a year ago!):
> >
> > commit 12d560f4ea87030667438a169912380be00cea4b
> > Author: Paul E. McKenney <paulmck@linux•vnet.ibm.com>
> > Date: Tue Jul 14 18:35:23 2015 -0700
> >
> > rcu,locking: Privatize smp_mb__after_unlock_lock()
> >
> > RCU is the only thing that uses smp_mb__after_unlock_lock(), and is
> > likely the only thing that ever will use it, so this commit makes this
> > macro private to RCU.
> >
> > Signed-off-by: Paul E. McKenney <paulmck@linux•vnet.ibm.com>
> > Cc: Will Deacon <will.deacon@arm•com>
> > Cc: Peter Zijlstra <peterz@infradead•org>
> > Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> > Cc: "linux-arch@vger•kernel.org" <linux-arch@vger•kernel.org>
> >
> > So I concur and I'm fine with your patch - or with the status quo code as well.
>
> I already have the patch queued, so how about I keep it if I get an ack
> from the powerpc guys and drop it otherwise?
Yeah, sounds good! Your patch made me look up 'RelAcq' so it has documentation
value as well ;-)
Thanks,
Ingo
next prev parent reply other threads:[~2017-01-15 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170114091941.GA22961@linux.vnet.ibm.com>
[not found] ` <1484385601-23379-2-git-send-email-paulmck@linux.vnet.ibm.com>
[not found] ` <20170114093550.GB14970@gmail.com>
[not found] ` <20170114195417.GW5238@linux.vnet.ibm.com>
2017-01-14 21:41 ` [PATCH tip/core/rcu 2/3] srcu: Force full grace-period ordering Paul E. McKenney
2017-01-15 7:11 ` Ingo Molnar
2017-01-15 7:40 ` Paul E. McKenney
2017-01-15 7:57 ` Ingo Molnar
2017-01-15 9:24 ` Paul E. McKenney
2017-01-15 9:40 ` Ingo Molnar [this message]
2017-01-15 19:45 ` Paul E. McKenney
2017-01-16 6:56 ` Ingo Molnar
2017-01-23 8:12 ` Michael Ellerman
2017-01-24 2:45 ` Paul E. McKenney
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=20170115094058.GB28621@gmail.com \
--to=mingo@kernel$(echo .)org \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bobby.prani@gmail$(echo .)com \
--cc=boqun.feng@linux$(echo .)vnet.ibm.com \
--cc=dhowells@redhat$(echo .)com \
--cc=dipankar@in$(echo .)ibm.com \
--cc=dvhart@linux$(echo .)intel.com \
--cc=edumazet@google$(echo .)com \
--cc=fweisbec@gmail$(echo .)com \
--cc=jiangshanlai@gmail$(echo .)com \
--cc=josh@joshtriplett$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=oleg@redhat$(echo .)com \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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