From: Aaron Tomlin <atomlin@atomlin.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org
Cc: riel@surriel.com, frederic@kernel.org, atomlin@atomlin.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] tick/nohz: Expose housekeeping CPUs in sysfs
Date: Mon, 6 Oct 2025 21:29:57 -0400 [thread overview]
Message-ID: <20251007012958.16666-1-atomlin@atomlin.com> (raw)
Expose the current system-defined list of housekeeping CPUs in a new
sysfs file: /sys/devices/system/cpu/housekeeping.
This provides userspace performance tuning tools and resource managers
with a canonical, reliable method to accurately identify the cores
responsible for essential kernel maintenance workloads (RCU, timer
callbacks, and unbound workqueues). Currently, tooling must manually
calculate the housekeeping set by parsing complex kernel boot parameters
(like isolcpus= and nohz_full=) and system topology, which is prone to
error. This dedicated file simplifies the configuration of low-latency
workloads.
Changes since v1 [1]:
- Refactor to use an if statement (Greg KH)
- Use DEVICE_ATTR_RO() instead (Greg KH)
- Document the new file under Documentation/ABI (Greg KH)
[1]: https://lore.kernel.org/lkml/20251006005853.76335-1-atomlin@atomlin.com/
Aaron Tomlin (1):
tick/nohz: Expose housekeeping CPUs in sysfs
.../ABI/testing/sysfs-devices-system-cpu | 11 +++++++++++
drivers/base/cpu.c | 15 +++++++++++++++
2 files changed, 26 insertions(+)
--
2.49.0
next reply other threads:[~2025-10-07 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 1:29 Aaron Tomlin [this message]
2025-10-07 1:29 ` [PATCH v2 1/1] tick/nohz: Expose housekeeping CPUs in sysfs Aaron Tomlin
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=20251007012958.16666-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=dakr@kernel.org \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=riel@surriel.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 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.