All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Christoph Lameter" <cl@linux.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Thomas Gleixner" <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Dang Huynh" <danct12@riseup.net>
Subject: Is kernel/Kconfig.hz still up-to-date?
Date: Mon, 07 Apr 2025 15:27:21 +0200	[thread overview]
Message-ID: <D90FWJ3O72ML.2DA83AXPJCR3Q@cknow.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]

Hi,

I recently had a discussion about the use of HZ_1000 in the kernel
configuration and the impact on performance.
My reading of the HZ_1000 help text tells me that HZ_1000 is primarily
useful for DAW and other systems where RT capabilities are (most)
important. This is due to "systems requiring fast interactive responses
to events", whereby I put the emphasis on *requiring*.

As *I* understand the rest of the help texts, a higher Hz value can/will
have a negative effect on f.e. IO performance. And I'm not entirely
sure, but it seems each CPU (core?) multiplies the nr of interrupts?

But, doing a ``git blame`` on the choices shows that apart from a
spelling fix in 2025, all the text hasn't changed since 2005/2006.
But a LOT has changed since then. There are more architectures and the
hardware and the kernel itself have changed quite a bit since then.

While the Kconfig.hz default is still HZ_250, the x86 defconfig changed
to HZ_1000 in 5cb04df8d3f0 ("x86: defconfig updates") (in 2008) and
there are various distros which have switched to HZ_1000.

So my questions are: are the Kconfig help text still accurate for
current (hardware) systems and kernels? Is HZ_250 still the most
sensible default? Or is the 'newer' HZ_300 better? Or even HZ_1000?
And does that apply only for x86 or for all architectures?
(distros seem to vary between architectures f.e.)

Cheers,
  Diederik

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2025-04-07 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 13:27 Diederik de Haas [this message]
2025-04-08 16:42 ` Is kernel/Kconfig.hz still up-to-date? Christoph Lameter (Ampere)

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=D90FWJ3O72ML.2DA83AXPJCR3Q@cknow.org \
    --to=didi.debian@cknow.org \
    --cc=akpm@linux-foundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=cl@linux.com \
    --cc=danct12@riseup.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.