From: David Laight <david.laight.linux@gmail.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Stultz <jstultz@google.com>,
Saravana Kannan <saravanak@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Frederic Weisbecker <frederic@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig.hz: Change default HZ to 1000
Date: Sun, 16 Feb 2025 19:05:40 +0000 [thread overview]
Message-ID: <20250216190540.254512a5@pumpkin> (raw)
In-Reply-To: <20250210001915.123424-1-qyousef@layalina.io>
On Mon, 10 Feb 2025 00:19:15 +0000
Qais Yousef <qyousef@layalina.io> wrote:
> The frequency at which TICK happens is very important from scheduler
> perspective. There's a responsiveness trade-of that for interactive
> systems the current default is set too low.
The problem I see is that most people use a kernel from one of the distributions.
So you need to persuade them to change their default.
Change the default 'default' won't necessarily have any effect.
OTOH if you decouple the timer interrupt rate from HZ (or jiffies)
then it becomes possible to boot time (or even run-time) change
the timer interrupt rate.
So it makes much more sense to fix 'jiffies' as a 1ms counter and then
configure the timer interrupt to be a number of ms/jiffies.
This would be similar all the simplifications that came about by making
the high precision timestamps (etc) ns regardless of the actual
resolution on any specific hardware.
David
next prev parent reply other threads:[~2025-02-16 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 0:19 [PATCH] Kconfig.hz: Change default HZ to 1000 Qais Yousef
2025-02-12 14:50 ` Joel Fernandes
2025-02-16 16:11 ` Qais Yousef
2025-02-23 7:50 ` Andrea Righi
2025-02-23 10:00 ` Ingo Molnar
2025-02-23 23:21 ` Qais Yousef
2025-02-24 13:16 ` Vincent Guittot
2025-02-24 23:23 ` Sean Christopherson
2025-02-13 8:24 ` Saravana Kannan
2025-02-16 16:29 ` Qais Yousef
2025-02-16 19:05 ` David Laight [this message]
2025-02-22 23:47 ` Qais Yousef
2025-02-28 10:33 ` Attila Fazekas
2025-03-02 12:05 ` David Laight
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=20250216190540.254512a5@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
/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