From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
Uladzislau Rezki <urezki@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: [PATCH 0/4] rcu/nocb cleanups
Date: Thu, 25 Apr 2024 16:18:31 +0200 [thread overview]
Message-ID: <20240425141835.19776-1-frederic@kernel.org> (raw)
Hi,
Some cleanups before converting (de-)offloading to only work on offline
CPUs.
Frederic Weisbecker (4):
rcu/nocb: Fix segcblist state machine comments about bypass
rcu/nocb: Fix segcblist state machine stale comments about timers
rcu/nocb: Use kthread parking instead of ad-hoc implementation
rcu/nocb: Remove buggy bypass lock contention mitigation
include/linux/rcu_segcblist.h | 88 +++++++++-----------
kernel/rcu/tree.h | 1 -
kernel/rcu/tree_nocb.h | 149 ++++++++++------------------------
3 files changed, 79 insertions(+), 159 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-25 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 14:18 Frederic Weisbecker [this message]
2024-04-25 14:18 ` [PATCH 1/4] rcu/nocb: Fix segcblist state machine comments about bypass Frederic Weisbecker
2024-04-25 14:18 ` [PATCH 2/4] rcu/nocb: Fix segcblist state machine stale comments about timers Frederic Weisbecker
2024-04-25 14:18 ` [PATCH 3/4] rcu/nocb: Use kthread parking instead of ad-hoc implementation Frederic Weisbecker
2024-04-25 14:18 ` [PATCH 4/4] rcu/nocb: Remove buggy bypass lock contention mitigation Frederic Weisbecker
2024-04-29 21:02 ` [PATCH 0/4] rcu/nocb cleanups 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=20240425141835.19776-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@amd.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.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 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.