From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Theodore Tso <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
Gabriele Paoloni <gpaoloni@redhat.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Chuck Wolber <chuckwolber@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Chris Mason <clm@meta.com>,
linux-kernel@vger.kernel.org
Subject: Re: Follow-up on Linux-kernel code accessibility
Date: Mon, 29 Dec 2025 22:05:15 +0000 [thread overview]
Message-ID: <aVL7G55hAhyplgQz@gallifrey> (raw)
In-Reply-To: <20251229153517.0001e755@gandalf.local.home>
* Steven Rostedt (rostedt@goodmis.org) wrote:
> There's nothing there that says "3" is needed. Why divide at all? Why not
> just add 1?
Now while Paul obviously doesn't want to tell us, I decided I should
do what someone who actually cared would do, and looked at the git history,
To my surprise, I see I made a mistake - the three magic constants
in this function were all added separately, and the two uses of '3'
are not necessarily the same.
8c7c4829a8 - from 2016
rcu: Awaken grace-period kthread if too long since FQS
says it's a crude hack but doesn't mention why it chose 3 in the commit
message; among other stuff it adds:
+ WRITE_ONCE(rsp->jiffies_kick_kthreads,
+ jiffies + 3 * j);
9cf422a8 - from 2018
rcu: Accommodate zero jiffies_till_first_fqs and kthread kicking
replaces that:
- jiffies + 3 * j);
+ jiffies + (j ? 3 * j : 2));
to stop using too much cpu and says 'at least two jiffies'
fb77dcc - from 2022
rcu: Decrease FQS scan wait time in case of callback overloading
introduces the:
j = (j + 2) / 3;
and commit message says:
This commit therefore divides the normal time between rescans by three,
rounding up. Thus a small system running at HZ=1000 that is suffering
from callback overload will wait only one jiffy instead of the normal
three between rescans.
So that one does have a commit message explanation at least; although
I'm not sure I know where the 'normal three' comes from - but I guess
that's followable eventually.
But heck, this is making it hard to find them.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-12-29 22:05 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 19:49 Follow-up on Linux-kernel code accessibility Paul E. McKenney
2025-12-18 22:09 ` David Laight
2025-12-19 0:20 ` Paul E. McKenney
2025-12-19 6:51 ` Julia Lawall
2025-12-19 17:09 ` Theodore Tso
2025-12-19 17:59 ` Sasha Levin
2025-12-19 18:28 ` Steven Rostedt
2025-12-20 0:36 ` Paul E. McKenney
2025-12-22 15:42 ` Steven Rostedt
2025-12-23 23:46 ` Paul E. McKenney
2025-12-24 14:11 ` Steven Rostedt
2025-12-25 15:03 ` Theodore Tso
2025-12-25 18:22 ` Paul E. McKenney
2025-12-26 16:48 ` Steven Rostedt
2025-12-26 18:44 ` Paul E. McKenney
2025-12-26 19:22 ` Theodore Tso
2025-12-26 20:35 ` Steven Rostedt
2025-12-27 1:04 ` Paul E. McKenney
2025-12-27 6:16 ` Julia Lawall
2025-12-27 23:28 ` Paul E. McKenney
2025-12-27 23:32 ` Julia Lawall
2025-12-28 1:26 ` Paul E. McKenney
2025-12-28 1:48 ` Dr. David Alan Gilbert
2025-12-28 5:16 ` Paul E. McKenney
2025-12-28 9:36 ` Julia Lawall
2025-12-29 15:40 ` Steven Rostedt
2025-12-29 16:16 ` Paul E. McKenney
2025-12-29 17:02 ` Dr. David Alan Gilbert
2025-12-29 17:37 ` Paul E. McKenney
2025-12-29 18:10 ` Dr. David Alan Gilbert
2025-12-29 18:59 ` Paul E. McKenney
2025-12-29 20:35 ` Steven Rostedt
2025-12-29 22:05 ` Dr. David Alan Gilbert [this message]
2026-01-09 1:35 ` Paul E. McKenney
2026-01-09 1:34 ` Paul E. McKenney
2026-01-09 14:58 ` Steven Rostedt
2026-01-09 18:31 ` Paul E. McKenney
2026-01-11 3:30 ` Theodore Tso
2026-01-11 17:11 ` Steven Rostedt
2026-01-12 5:06 ` Paul E. McKenney
2026-01-12 7:05 ` Julia Lawall
2026-01-12 16:57 ` Paul E. McKenney
2025-12-29 23:50 ` Theodore Tso
2025-12-30 0:19 ` Steven Rostedt
2025-12-30 0:34 ` Steven Rostedt
2026-01-09 2:23 ` Paul E. McKenney
2025-12-28 12:46 ` Dr. David Alan Gilbert
2025-12-29 0:03 ` Paul E. McKenney
2025-12-25 18:18 ` Paul E. McKenney
2025-12-26 16:51 ` Steven Rostedt
2025-12-26 18:36 ` Paul E. McKenney
2025-12-19 21:05 ` Chris Mason
2025-12-20 4:00 ` Theodore Tso
2026-01-06 18:08 ` Lorenzo Stoakes
2026-01-13 13:03 ` Chris Mason
2025-12-20 0:31 ` Paul E. McKenney
2026-01-06 18:05 ` Lorenzo Stoakes
2026-01-09 1:40 ` 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=aVL7G55hAhyplgQz@gallifrey \
--to=dave@treblig.org \
--cc=chuckwolber@gmail.com \
--cc=clm@meta.com \
--cc=dvyukov@google.com \
--cc=gpaoloni@redhat.com \
--cc=julia.lawall@inria.fr \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mark.rutland@arm.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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