From: torvic9@mailbox.org
To: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"nsc@kernel.org" <nsc@kernel.org>
Subject: [QUESTION] kernel/Kconfig.hz: outdated help texts?
Date: Fri, 24 Apr 2026 10:18:44 +0200 (CEST) [thread overview]
Message-ID: <1896318894.249754.1777018724256@app.mailbox.org> (raw)
Hello,
I noticed that the help text in kernel/Kconfig.hz has barely changed since
configurable frequency of the timer was introduced in 2005.
Are these help texts still accurate 21 years later?
We have e.g.:
"250 Hz is a good compromise choice allowing server performance
while also showing good interactive responsiveness even
on SMP and NUMA systems. If you are going to be using NTSC video
or multimedia, select 300 Hz instead."
Is that NTSC/PAL thing still relevant today, in times of high resolution timers,
modern graphics cards, Freesync and high-refresh 4K monitors with 144 Hz?
Cheers,
Tor Vic
next reply other threads:[~2026-04-24 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 8:18 torvic9 [this message]
2026-04-24 18:29 ` [QUESTION] kernel/Kconfig.hz: outdated help texts? Nathan Chancellor
2026-04-27 21:14 ` John Stultz
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=1896318894.249754.1777018724256@app.mailbox.org \
--to=torvic9@mailbox.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.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