From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Frederic Weisbecker <frederic@kernel.org>,
Michal Hocko <mhocko@suse.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Marco Crivellari <marco.crivellari@suse.com>
Subject: [PATCH] doc: Update residual 1Hz handling description
Date: Mon, 12 Jan 2026 17:39:01 +0100 [thread overview]
Message-ID: <20260112163901.338596-1-marco.crivellari@suse.com> (raw)
When a CPU is nohz there is a residual 1Hz that must be handled.
Accordingly to the documentation, this should be manually affined to
housekeeping.
This is no longer the case: the residual 1Hz is automatically offloaded
to workqueues already affined to housekeeping CPUs.
So change the documentation accordingly.
Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
---
Documentation/admin-guide/kernel-parameters.txt | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 902ecd92a29f..414fb42786c7 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2368,15 +2368,8 @@
nohz
Disable the tick when a single task runs.
- A residual 1Hz tick is offloaded to workqueues, which you
- need to affine to housekeeping through the global
- workqueue's affinity configured via the
- /sys/devices/virtual/workqueue/cpumask sysfs file, or
- by using the 'domain' flag described below.
-
- NOTE: by default the global workqueue runs on all CPUs,
- so to protect individual CPUs the 'cpumask' file has to
- be configured manually after bootup.
+ A residual 1Hz tick is offloaded to workqueues, already
+ affined to housekeeping CPUs.
domain
Isolate from the general SMP balancing and scheduling
--
2.52.0
reply other threads:[~2026-01-12 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260112163901.338596-1-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.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