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@joelfernandes.org
Subject: [PATCH tip/core/rcu 0/2] Expedited grace-period changes for v4.19
Date: Mon, 25 Jun 2018 15:43:08 -0700 [thread overview]
Message-ID: <20180625224308.GA10064@linux.vnet.ibm.com> (raw)
Hello!
This series contains a couple of changes to RCU expedited grace periods:
1. Initialize the last rcu_node structure via direct call rather than
via workqueue.
2. Make parallel initialization of parallel grace periods handle the
possibility of CPU 0 begin offline, courtesy of Boqun Feng.
(This is currently marked Not-Yet-Signed-off-by while looking
into the possibility of a more efficient implementation.)
Thanx, Paul
------------------------------------------------------------------------
rcu.h | 3 +++
tree_exp.h | 21 +++++++++++++++++----
2 files changed, 20 insertions(+), 4 deletions(-)
next reply other threads:[~2018-06-25 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 22:43 Paul E. McKenney [this message]
2018-06-25 22:43 ` [PATCH tip/core/rcu 1/2] rcu: Make expedited grace period use direct call on last leaf Paul E. McKenney
2018-06-25 22:43 ` [PATCH tip/core/rcu 2/2] rcu: Make expedited GPs handle CPU 0 being offline Paul E. McKenney
2018-06-26 9:38 ` Peter Zijlstra
2018-06-26 10:44 ` Boqun Feng
2018-06-26 11:46 ` Boqun Feng
2018-06-26 12:31 ` Paul E. McKenney
2018-06-26 19:27 ` Paul E. McKenney
2018-06-27 2:42 ` Boqun Feng
2018-06-27 16:15 ` Paul E. McKenney
2018-06-28 16:52 ` 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=20180625224308.GA10064@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@joelfernandes.org \
--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.