From: Joel Fernandes <joelagnelf@nvidia.com>
To: "Paul E . McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC v1 0/4] rcu/nocb: Clean ups and rcutorture test configs
Date: Tue, 24 Feb 2026 18:04:31 -0500 [thread overview]
Message-ID: <20260224230435.3390963-1-joelagnelf@nvidia.com> (raw)
This series contains clean ups for the RCU NOCB code and adds new
rcutorture test configurations for v7.1.
The first two patches consolidate duplicated code in the NOCB
implementation. The last two patches add new rcutorture configs:
- NOCB01 exercises CONFIG_RCU_LAZY combined with CONFIG_RCU_NOCB_CPU.
- NOCB02 exercises the rcu_nocb_poll polling mode code paths.
These configs are not added to CFLIST to avoid increasing default test
duration. The series passes overnight rcutorture testing.
Joel Fernandes (4):
rcu/nocb: Consolidate rcu_nocb_cpu_offload/deoffload functions
rcu/nocb: Extract nocb_bypass_needs_flush() to reduce duplication
rcutorture: Add NOCB01 config for RCU_LAZY torture testing
rcutorture: Add NOCB02 config for nocb poll mode testing
kernel/rcu/tree_nocb.h | 140 +++++++++++-------
.../selftests/rcutorture/configs/rcu/NOCB01 | 21 +++
.../rcutorture/configs/rcu/NOCB01.boot | 2 +
.../selftests/rcutorture/configs/rcu/NOCB02 | 20 +++
.../rcutorture/configs/rcu/NOCB02.boot | 3 +
5 files changed, 129 insertions(+), 57 deletions(-)
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB01
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB01.boot
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB02
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB02.boot
--
2.34.1
next reply other threads:[~2026-02-24 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 23:04 Joel Fernandes [this message]
2026-02-24 23:04 ` [PATCH RFC v1 1/4] rcu/nocb: Consolidate rcu_nocb_cpu_offload/deoffload functions Joel Fernandes
2026-03-04 15:32 ` Frederic Weisbecker
2026-03-04 17:05 ` Joel Fernandes
2026-02-24 23:04 ` [PATCH RFC v1 2/4] rcu/nocb: Extract nocb_bypass_needs_flush() to reduce duplication Joel Fernandes
2026-03-11 12:58 ` Frederic Weisbecker
2026-02-24 23:04 ` [PATCH RFC v1 3/4] rcutorture: Add NOCB01 config for RCU_LAZY torture testing Joel Fernandes
2026-03-11 13:02 ` Frederic Weisbecker
2026-02-24 23:04 ` [PATCH RFC v1 4/4] rcutorture: Add NOCB02 config for nocb poll mode testing Joel Fernandes
2026-02-25 21:47 ` Paul E. McKenney
2026-02-26 0:14 ` Joel Fernandes
2026-03-11 13:03 ` Frederic Weisbecker
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=20260224230435.3390963-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--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