[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151006193311.GS3910@linux.vnet.ibm.com>
Date: Tue, 6 Oct 2015 12:33:11 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Josh Triplett <josh@...htriplett.org>,
linux-kernel@...r.kernel.org, mingo@...nel.org,
jiangshanlai@...il.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
fweisbec@...il.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 0/13] percpu-rwsem patches for 4.4
On Tue, Oct 06, 2015 at 08:50:56PM +0200, Oleg Nesterov wrote:
> On 10/06, Josh Triplett wrote:
> >
> > For all 13:
> > Reviewed-by: Josh Triplett <josh@...htriplett.org>
>
> Thanks!
>
> > Regarding the rcu_sync infrastructure: odd that an atomic read
> > on the reader proves ligher weight than
> > rcu_read_lock()/rcu_read_unlock().
>
> Cough... Could you spell? ;) I am just curious and I can't understand
> what do you mean.
I would guess that Josh is thinking of CONFIG_PREEMPT=n and that you
worked with CONFIG_PREEMPT=y. But it would be good to get this fully
understood.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists