From: Aaron Tomlin <atomlin@atomlin.com>
To: oleg@redhat.com, frederic@kernel.org, peterz@infradead.org
Cc: nick.lange@gmail.com, seun.ewulomi@gmail.com,
mtosatti@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] sched/isolation: Warn when maxcpus= is specified with nohz_full= or isolcpus=
Date: Wed, 8 Jan 2025 21:14:45 +0000 (GMT) [thread overview]
Message-ID: <caabddb6-2c36-1372-e94c-9a50c659f5fb@atomlin.com> (raw)
In-Reply-To: <b51c2515-8cbc-ac7e-97ea-c6fd0e07cad6@atomlin.com>
On Sun, 1 Dec 2024, Aaron Tomlin wrote:
> Hi Oleg, Frederic, Peter,
>
> I have seen a case where maxcpus=1 and e.g. nohz_full=1,3-31, was used to
> force the CPU affinity of certain unbound or non CPU-specific kernel
> threads at boot-time. Albeit, since commit 9cc5b8656892a ("isolcpus: Affine
> unbound kernel threads to housekeeping cpus") this is handled entirely via
> nohz_full=. I thought it might be worth adding a warning.
>
>
> Aaron Tomlin (1):
> sched/isolation: Warn when maxcpus= is specified with nohz_full= or
> isolcpus=
>
> kernel/sched/isolation.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --
> 2.47.1
Hi Oleg, Frederic, Peter,
Any thoughts?
--
Aaron Tomlin
prev parent reply other threads:[~2025-01-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 18:42 Aaron Tomlin
2025-01-08 21:10 ` Aaron Tomlin
2025-01-08 21:14 ` Aaron Tomlin [this message]
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=caabddb6-2c36-1372-e94c-9a50c659f5fb@atomlin.com \
--to=atomlin@atomlin.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nick.lange@gmail.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=seun.ewulomi@gmail.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
all inboxes | Powered by JetHome®