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/10] Forward-progress changes for v4.20/v5.0
Date: Wed, 29 Aug 2018 16:00:35 -0700 [thread overview]
Message-ID: <20180829230035.GA7751@linux.vnet.ibm.com> (raw)
Hello!
This series includes changes that improve RCU's forward-progress
guarantees for normal grace periods, with a few stray RCU-consolidation
cleanups thrown in for good measure.
1. Make need_resched() respond to urgent RCU-QS needs.
2. Provide improved interrupt-from-idle check in rcu_check_callbacks().
3. Make rcutorture dump out the reader protection sequence when
an RCU failures or close calls occurs.
4. Motivate Tiny RCU forward progress.
5. Eliminate ->rcu_qs_ctr from the rcu_dynticks structure on account
of its no longer being used. And let that be a lesson to the
rest of that structure's fields!!!
6. Provide functions for determining if call_rcu() has been invoked
for debugging purposes by the users of call_rcu().
7. Compute jiffies_till_sched_qs from other kernel parameters,
because one size simply does not fit all.
8. More aggressively enlist scheduler aid for nohz_full CPUs.
After all, they might never see a scheduler-clock interrupt.
9. Avoid resched_cpu() when rescheduling the current CPU.
10. Convert "1UL << x" to "BIT(x)" to save a few characters.
Thanx, Paul
------------------------------------------------------------------------
Documentation/admin-guide/kernel-parameters.txt | 9 +
include/linux/rcupdate.h | 40 +++++
include/trace/events/rcu.h | 5
kernel/rcu/rcu.h | 5
kernel/rcu/rcutorture.c | 119 +++++++++++++---
kernel/rcu/tiny.c | 6
kernel/rcu/tree.c | 171 ++++++++++++++----------
kernel/rcu/tree.h | 6
kernel/rcu/tree_exp.h | 17 +-
kernel/rcu/tree_plugin.h | 14 +
10 files changed, 280 insertions(+), 112 deletions(-)
reply other threads:[~2018-08-29 23:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180829230035.GA7751@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.