From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
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/4] kfree_rcu() updates for v5.8
Date: Wed, 15 Apr 2020 10:19:24 -0700 [thread overview]
Message-ID: <20200415171924.GA9270@paulmck-ThinkPad-P72> (raw)
Hello!
This series updates kfree_rcu() testing and OOM handling. It also
provides a rcu_gp_might_be_stalled() function that judges whether or
not RCU is being stalled.
1. Add ability to increase object allocation size, courtesy
of Joel Fernandes.
2. rcu/tree: Add a shrinker to prevent OOM due to kfree_rcu()
batching, courtesy of Joel Fernandes.
3. rcu/tree: Count number of batched kfree_rcu() locklessly,
courtesy of Joel Fernandes.
4. Add rcu_gp_might_be_stalled() to indicate whether or not there
is currently a good chance that the current RCU grace period
is being stalled.
Thanx, Paul
------------------------------------------------------------------------
include/linux/rcutiny.h | 1
include/linux/rcutree.h | 1
kernel/rcu/rcuperf.c | 5 ++-
kernel/rcu/tree.c | 70 +++++++++++++++++++++++++++++++++++++++++++-----
kernel/rcu/tree_stall.h | 40 ++++++++++++++++++++++++---
5 files changed, 106 insertions(+), 11 deletions(-)
next reply other threads:[~2020-04-15 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 17:19 Paul E. McKenney [this message]
2020-04-15 17:19 ` [PATCH tip/core/rcu 1/4] rcuperf: Add ability to increase object allocation size paulmck
2020-04-15 17:19 ` [PATCH tip/core/rcu 2/4] rcu/tree: Add a shrinker to prevent OOM due to kfree_rcu() batching paulmck
2020-04-15 17:19 ` [PATCH tip/core/rcu 3/4] rcu/tree: Count number of batched kfree_rcu() locklessly paulmck
2020-04-15 17:19 ` [PATCH tip/core/rcu 4/4] rcu: Add rcu_gp_might_be_stalled() paulmck
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=20200415171924.GA9270@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--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=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).