From: Mike Galbraith <efault@gmx.de>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: question about isolcpus and nohz_full
Date: Fri, 10 Sep 2021 06:14:43 +0200 [thread overview]
Message-ID: <817e71d3987224bbacfd916b2d953fb528ecb4d5.camel@gmx.de> (raw)
In-Reply-To: <b39eca5b-98e4-6b9e-c65b-63aad84d8caf@windriver.com>
On Thu, 2021-09-09 at 10:26 -0600, Chris Friesen wrote:
>
> 2) Is it allowed to specify "nohz_full" for some CPUs at boot time
> without specifying any isolcpus?
Yup (IM[not the least bit;]HO the proper way to partition a box).
> If so, what happens if I later isolate
> a subset of those CPUs using "cpuset.sched_load_balance" in cgroups? Is
> that allowed when the equivalent boot args are not?
That's what an old shield script I still have laying around does. I
booted master on my little desktop box with nohz_full=1,2,3,5,6,7 and
shielded cores 2 and 3, after taking down cpus 4-7 (smt), and it still
seems to work fine.
I used to also override (via ugly.. maybe even fugly, hack) nohz
dynamically, turning the tick on/off for subsets, on having proven best
for jitter of heftily threaded RT app spread across many isolated
cores, thus could at need even partition a box with a mixture of
ticked, nohz idle, and tickless sets, albeit in a rather limited
fashion due to nohz_full preallocation requirement. Would be nice for
some situations if nohz mode were to become a fully dynamic set
attribute.
-Mike
prev parent reply other threads:[~2021-09-10 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 16:26 question about isolcpus and nohz_full Chris Friesen
2021-09-10 4:14 ` Mike Galbraith [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=817e71d3987224bbacfd916b2d953fb528ecb4d5.camel@gmx.de \
--to=efault@gmx.de \
--cc=chris.friesen@windriver.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).