From: Frederic Weisbecker <frederic@kernel.org>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
rcu@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH -next v1 10/16] rcu-tasks: Document that RCU Tasks Trace grace periods now imply RCU grace periods
Date: Wed, 18 Mar 2026 13:15:52 +0100 [thread overview]
Message-ID: <abqXeHifOg_hYeY3@localhost.localdomain> (raw)
In-Reply-To: <abqGt2CQCfM4PeqK@localhost.localdomain>
Le Wed, Mar 18, 2026 at 12:04:23PM +0100, Frederic Weisbecker a écrit :
> Le Tue, Mar 17, 2026 at 05:22:11PM -0400, Joel Fernandes a écrit :
> > From: "Paul E. McKenney" <paulmck@kernel.org>
> >
> > Now that RCU Tasks Trace is implemented in terms of SRCU-fast, the fact
> > that each SRCU-fast grace period implies at least two RCU grace periods
>
> two or one?
>
> AFAIU srcu_readers_active_idx_check() it's only one?
But as Paul just told me offline, we flip the idx so it's two. Sorry for the noise.
Thanks.
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2026-03-18 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260317212217.1527644-1-joelagnelf@nvidia.com>
2026-03-17 21:22 ` [PATCH -next v1 10/16] rcu-tasks: Document that RCU Tasks Trace grace periods now imply RCU grace periods Joel Fernandes
2026-03-18 11:04 ` Frederic Weisbecker
2026-03-18 12:15 ` Frederic Weisbecker [this message]
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=abqXeHifOg_hYeY3@localhost.localdomain \
--to=frederic@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.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=skhan@linuxfoundation.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