From: Oleg Nesterov <oleg@redhat.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, bobby.prani@gmail.com
Subject: Re: [PATCH tip/core/rcu 0/13] percpu-rwsem patches for 4.4
Date: Tue, 6 Oct 2015 20:50:56 +0200 [thread overview]
Message-ID: <20151006185055.GA15844@redhat.com> (raw)
In-Reply-To: <20151006174226.GK9600@cloud>
On 10/06, Josh Triplett wrote:
>
> For all 13:
> Reviewed-by: Josh Triplett <josh@joshtriplett.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.
Oleg.
next prev parent reply other threads:[~2015-10-06 18:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 16:45 [PATCH tip/core/rcu 0/13] percpu-rwsem patches for 4.4 Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 01/13] locktorture: Support rtmutex torturing Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 02/13] locking/percpu-rwsem: Export symbols for locktorture Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 03/13] locktorture: Add torture tests for percpu_rwsem Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 04/13] torture: Consolidate cond_resched_rcu_qs() into stutter_wait() Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 05/13] rcu: Create rcu_sync infrastructure Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 06/13] rcu_sync: Simplify rcu_sync using new rcu_sync_ops structure Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 07/13] rcu_sync: Add CONFIG_PROVE_RCU checks Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 08/13] rcu_sync: Introduce rcu_sync_dtor() Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 09/13] locking/percpu-rwsem: Make percpu_free_rwsem() after kzalloc() safe Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 10/13] locking/percpu-rwsem: Make use of the rcu_sync infrastructure Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 11/13] locking/percpu-rwsem: Fix the comments outdated by rcu_sync Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 12/13] locking/percpu-rwsem: Clean up the lockdep annotations in percpu_down_read() Paul E. McKenney
2015-10-06 16:45 ` [PATCH tip/core/rcu 13/13] rcu_sync: Cleanup the CONFIG_PROVE_RCU checks Paul E. McKenney
2015-10-06 17:42 ` [PATCH tip/core/rcu 0/13] percpu-rwsem patches for 4.4 Josh Triplett
2015-10-06 18:50 ` Oleg Nesterov [this message]
2015-10-06 19:33 ` Paul E. McKenney
2015-10-06 20:36 ` Josh Triplett
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=20151006185055.GA15844@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.