From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@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
Subject: [PATCH tip/core/rcu 0/2] Enforce RCU grace-period transitivity
Date: Fri, 4 Dec 2015 15:41:25 -0800 [thread overview]
Message-ID: <20151204234125.GA21380@linux.vnet.ibm.com> (raw)
Hello!
Within RCU, acquisitions of the rcu_node structure's ->lock field must
be followed by smp_mb__after_unlock_lock() in order to enforce RCU's
grace-period memory-ordering guarantees. In theory, acquisitions for
debug purposes need not have smp_mb__after_unlock_lock(), but in practice,
anything other than fully consistent enforcement of this rule is a recipe
for disaster. This series therefore adds smp_mb__after_unlock_lock()
for consistency:
1. Create wrapper functions to minimize the number of these
smp_mb__after_unlock_lock() calls, and apply these wrapper
functions throughout. Courtesy of Peter Zijlstra.
2. Catch up wrapper-function application to patches that were
in flight at the time #1 was created.
Thanx, Paul
------------------------------------------------------------------------
b/kernel/rcu/tree.c | 102 ++++++++++++++++-----------------------------
b/kernel/rcu/tree.h | 39 +++++++++++++++++
b/kernel/rcu/tree_plugin.h | 20 +++-----
b/kernel/rcu/tree_trace.c | 2
4 files changed, 85 insertions(+), 78 deletions(-)
next reply other threads:[~2015-12-04 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 23:41 Paul E. McKenney [this message]
2015-12-04 23:42 ` [PATCH tip/core/rcu 1/2] rcu: Create transitive rnp->lock acquisition functions Paul E. McKenney
2015-12-04 23:42 ` [PATCH tip/core/rcu 2/2] rcu: Add transitivity to remaining rcu_node ->lock acquisitions 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=20151204234125.GA21380@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.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=oleg@redhat.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.