From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>
Subject: Re: [PATCH 1/3] rcu: Replace magic number with meaningful constant in rcu_seq_done_exact()
Date: Tue, 1 Apr 2025 15:38:21 +0200 [thread overview]
Message-ID: <Z-vsTRydjIAK-4-d@localhost.localdomain> (raw)
In-Reply-To: <bc4d930e-60c2-4ff8-8995-d463b6365b00@paulmck-laptop>
Le Mon, Mar 31, 2025 at 02:29:52PM -0700, Paul E. McKenney a écrit :
> The disagreement is a feature, at least up to a point. That feature
> allows CPUs to go idle for long periods without RCU having to bother
> them or to mess with their per-CPU data (give or take ->gpwrap). It also
> allows per-rcu_node-leaf locking, which is important on large systems.
>
> Trying to make precisely globally agreed-on beginnings and ends of
> RCU grace periods will not end well from performance, scalability,
> or real-time-response viewpoints. ;-)
The distributed disagreement is definetly a feature. The duplicate root
is more debatable.
> But simplifications that don't hurt performance, scalability, and
> real-time-response are of course welcome.
I'm not even sure my proposal is a simplification. Perhaps it is. Another
hope is that it could avoid future accidents.
> Indeed, this probably needs actual performance results showing that
> it is needed. My guess is that only systems with a single rcu_node
> structure that is both leaf and root would have any chance of noticing.
> And those tend to have few CPUs, so they might not care.
Do you have any idea for a benchmark to test here?
Thanks.
> Thanx, Paul
next prev parent reply other threads:[~2025-04-01 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:01 [PATCH 0/3] rcu_seq_done_exact() improvements Joel Fernandes
2025-03-24 17:01 ` [PATCH 1/3] rcu: Replace magic number with meaningful constant in rcu_seq_done_exact() Joel Fernandes
2025-03-26 22:33 ` Paul E. McKenney
2025-03-26 22:42 ` Joel Fernandes
2025-03-27 17:09 ` Paul E. McKenney
2025-03-28 2:31 ` Joel Fernandes
2025-03-30 22:10 ` Frederic Weisbecker
2025-03-31 18:28 ` Paul E. McKenney
2025-03-31 21:14 ` Frederic Weisbecker
2025-03-31 21:29 ` Paul E. McKenney
2025-04-01 13:38 ` Frederic Weisbecker [this message]
2025-04-02 4:24 ` Paul E. McKenney
2025-03-24 17:01 ` [PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working Joel Fernandes
2025-03-26 22:36 ` Paul E. McKenney
2025-03-26 22:50 ` Joel Fernandes
2025-03-26 23:21 ` Paul E. McKenney
2025-03-24 17:01 ` [PATCH 3/3] rcu: Comment on the extraneous delta test on rcu_seq_done_exact() Joel Fernandes
2025-03-26 22:37 ` Paul E. McKenney
2025-03-26 22:51 ` Joel Fernandes
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=Z-vsTRydjIAK-4-d@localhost.localdomain \
--to=frederic@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=joelagnelf@nvidia.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.zhang1211@gmail.com \
--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).