From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
To: linux-kernel@vger.kernel.org
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
Ingo Molnar <mingo@redhat.com>,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
neeraj.iitr10@gmail.com, "Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>
Subject: [PATCH v6 0/4] Add support for length of each segment in the segcblist
Date: Wed, 23 Sep 2020 11:22:07 -0400 [thread overview]
Message-ID: <20200923152211.2403352-1-joel@joelfernandes.org> (raw)
This is required for several usecases identified. One of them being tracing how
the segmented callback list changes. Tracing this has identified issues in RCU
code in the past.
From Paul:
Another use case is of course more accurately determining whether a given CPU's
large pile of callbacks can be best served by making grace periods go faster,
invoking callbacks more vigorously, or both. It should also be possible to
simplify some of the callback handling a bit, given that some of the unnatural
acts are due to there having been no per-batch counts.
Revision history:
v6: Fixed TREE04, and restored older logic to ensure rcu_barrier works.
v5: Various changes, bug fixes. Discovery of rcu_barrier issue.
v4: Restructured rcu_do_batch() and segcblist merging to avoid issues.
Fixed minor nit from Davidlohr.
v1->v3: minor nits.
(https://lore.kernel.org/lkml/20200719034210.2382053-1-joel@joelfernandes.org/)
Joel Fernandes (Google) (4):
rcu/tree: Make rcu_do_batch count how many callbacks were executed
rcu/segcblist: Add counters to segcblist datastructure
rcu/trace: Add tracing for how segcb list changes
rcu/segcblist: Remove useless rcupdate.h include
include/linux/rcu_segcblist.h | 2 +
include/trace/events/rcu.h | 25 ++++++
kernel/rcu/rcu_segcblist.c | 161 +++++++++++++++++++++++++---------
kernel/rcu/rcu_segcblist.h | 8 +-
kernel/rcu/tree.c | 18 ++--
5 files changed, 165 insertions(+), 49 deletions(-)
--
2.28.0.681.g6f77f65b4e-goog
next reply other threads:[~2020-09-23 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 15:22 Joel Fernandes (Google) [this message]
2020-09-23 15:22 ` [PATCH v6 1/4] rcu/tree: Make rcu_do_batch count how many callbacks were executed Joel Fernandes (Google)
2020-10-09 23:14 ` Frederic Weisbecker
2020-10-11 16:35 ` Joel Fernandes
2020-10-12 13:50 ` Paul E. McKenney
2020-10-14 15:06 ` Neeraj Upadhyay
2020-10-14 15:23 ` joel
2020-09-23 15:22 ` [PATCH v6 2/4] rcu/segcblist: Add counters to segcblist datastructure Joel Fernandes (Google)
2020-10-12 23:20 ` Frederic Weisbecker
2020-10-14 15:25 ` joel
2020-10-14 23:09 ` joel
2020-09-23 15:22 ` [PATCH v6 3/4] rcu/trace: Add tracing for how segcb list changes Joel Fernandes (Google)
2020-10-14 15:22 ` Neeraj Upadhyay
2020-10-15 0:05 ` joel
2020-09-23 15:22 ` [PATCH v6 4/4] rcu/segcblist: Remove useless rcupdate.h include Joel Fernandes (Google)
2020-09-24 23:42 ` [PATCH v6 0/4] Add support for length of each segment in the segcblist 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=20200923152211.2403352-1-joel@joelfernandes.org \
--to=joel@joelfernandes.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=neeraj.iitr10@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
/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).