From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: Pranith Kumar <bobby.prani@gmail.com>,
Christoph Lameter <cl@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 09/16] percpu: Replace smp_read_barrier_depends() with lockless_dereference()
Date: Sun, 16 Nov 2014 20:43:00 -0800 [thread overview]
Message-ID: <20141117044300.GM4460@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141114131448.GC21209@htj.dyndns.org>
On Fri, Nov 14, 2014 at 08:14:48AM -0500, Tejun Heo wrote:
> On Thu, Nov 13, 2014 at 02:24:15PM -0500, Pranith Kumar wrote:
> > Recently lockless_dereference() was added which can be used in place of
> > hard-coding smp_read_barrier_depends(). The following PATCH makes the change.
> >
> > Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
>
> How should this be routed? There's a pending change on the same
> region of code and if this patch is routed outside percpu tree it'd
> cause a conflict and I can't route this as lockless_dereference()
> isn't in the mainline yet. Maybe expose a git branch which contaisn
> lockless_dereference() so that percpu can pull it in?
Actually, lockless_dereference() is now in mainline, if that makes it
easier.
Thanx, Paul
next prev parent reply other threads:[~2014-11-17 4:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 19:24 [RFC PATCH 00/16] Replace smp_read_barrier_depends() with lockless_derefrence() Pranith Kumar
2014-11-13 19:24 ` [PATCH 01/16] crypto: caam - Remove unnecessary smp_read_barrier_depends() Pranith Kumar
2014-11-13 20:10 ` Paul E. McKenney
[not found] ` <546527D0.9040806@gmail.com>
2014-11-14 0:58 ` Kim Phillips
2014-11-13 19:24 ` [PATCH 02/16] doc: memory-barriers.txt: Document use of lockless_dereference() Pranith Kumar
2014-11-13 20:11 ` Paul E. McKenney
2014-11-13 19:24 ` [PATCH 03/16] drivers: dma: Replace smp_read_barrier_depends() with lockless_dereference() Pranith Kumar
2014-11-13 19:24 ` [PATCH 04/16] dcache: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 05/16] overlayfs: " Pranith Kumar
2014-11-17 10:35 ` Miklos Szeredi
2014-11-13 19:24 ` [PATCH 06/16] assoc_array: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 07/16] hyperv: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 08/16] rcupdate: " Pranith Kumar
2014-11-18 17:16 ` Paul E. McKenney
2014-11-18 19:38 ` Pranith Kumar
2014-11-13 19:24 ` [PATCH 09/16] percpu: " Pranith Kumar
2014-11-14 13:14 ` Tejun Heo
2014-11-14 16:02 ` Pranith Kumar
2014-11-17 4:43 ` Paul E. McKenney [this message]
2014-11-13 19:24 ` [PATCH 10/16] perf: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 11/16] seccomp: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 12/16] task_work: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 13/16] ksm: " Pranith Kumar
2014-11-30 22:34 ` Hugh Dickins
2014-11-13 19:24 ` [PATCH 14/16] slab: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 15/16] netfilter: " Pranith Kumar
2014-11-13 19:24 ` [PATCH 16/16] rxrpc: " Pranith Kumar
2014-11-13 20:07 ` [RFC PATCH 00/16] Replace smp_read_barrier_depends() with lockless_derefrence() Paul E. McKenney
2014-11-13 20:11 ` [PATCH 06/16] assoc_array: Replace smp_read_barrier_depends() with lockless_dereference() David Howells
2014-11-13 20:17 ` [PATCH 16/16] rxrpc: " David Howells
2014-11-13 20:47 ` David Howells
2014-11-13 21:55 ` Pranith Kumar
2014-11-13 23:07 ` David Howells
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=20141117044300.GM4460@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).