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,
fweisbec@gmail.com, oleg@redhat.com, joel.opensrc@gmail.com
Subject: [PATCH tip/core/rcu 0/3] Parallelize expedited grace periods for v4.18
Date: Sun, 22 Apr 2018 19:20:47 -0700 [thread overview]
Message-ID: <20180423022047.GA20189@linux.vnet.ibm.com> (raw)
Hello!
This series parallelizes grace-period initialization for expedited
grace periods and adds a couple of fixes:
1. Parallelize expedited grace-period initialization in order to
reduce the growth of latency with increasing numbers of CPUs.
2. Updates comments on which locks are to be held to match the
code, courtesy of Boqun Feng.
3. Protect all calls to sync_rcu_preempt_exp_done() with the
corresponding rcu_node structure's ->lock held, courtesy of
Boqun Feng.
Thanx, Paul
------------------------------------------------------------------------
rcu.h | 1
tree.c | 3
tree.h | 10 ++
tree_exp.h | 222 ++++++++++++++++++++++++++++++++++++-------------------------
4 files changed, 148 insertions(+), 88 deletions(-)
next reply other threads:[~2018-04-23 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 2:20 Paul E. McKenney [this message]
2018-04-23 2:21 ` [PATCH tip/core/rcu 1/3] rcu: Parallelize expedited grace-period initialization Paul E. McKenney
2018-04-23 2:21 ` [PATCH tip/core/rcu 2/3] rcu: exp: Fix "must hold exp_mutex" comments for QS reporting functions Paul E. McKenney
2018-04-23 2:21 ` [PATCH tip/core/rcu 3/3] rcu: exp: Protect all sync_rcu_preempt_exp_done() with rcu_node lock 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=20180423022047.GA20189@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel.opensrc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox