From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Adam Li <adamli@os.amperecomputing.com>,
anna-maria@linutronix.de, tglx@linutronix.de, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, vschneid@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, patches@amperecomputing.com
Subject: Re: [PATCH RESEND 1/2] tick/nohz: Fix wrong NOHZ idle CPU state
Date: Mon, 8 Sep 2025 08:25:48 -0700 (PDT) [thread overview]
Message-ID: <8fcea325-ca5f-0abd-34e0-1ac7b092e2fb@gentwo.org> (raw)
In-Reply-To: <aLrN4KQ1vDsqRTwM@localhost.localdomain>
On Fri, 5 Sep 2025, Frederic Weisbecker wrote:
> isolcpus for domain isolation is indeed in the way for long term deprecation
> and the only replacement possible is cpuset, which overhead is only visible
> on partition creation and update.
>
> We could argue on the interface, the point is that nohz_full doesn't make sense
> without domain isolation.
Most use cases I see use nohz_full on all cpus and rely on the OS to
exempt the sheperd cpu.
next prev parent reply other threads:[~2025-09-08 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 4:27 [PATCH RESEND 0/2] tick/nohz: CPU cannot enter NOHZ idle balance state Adam Li
2025-08-21 4:27 ` [PATCH RESEND 1/2] tick/nohz: Fix wrong NOHZ idle CPU state Adam Li
2025-09-04 16:05 ` Frederic Weisbecker
2025-09-04 16:10 ` Christoph Lameter (Ampere)
2025-09-05 11:47 ` Frederic Weisbecker
2025-09-08 15:25 ` Christoph Lameter (Ampere) [this message]
2026-02-11 23:19 ` Shubhang Kaushik
2025-08-21 4:27 ` [PATCH RESEND 2/2] tick/nohz: Trigger warning when CPU in wrong NOHZ idle state Adam Li
2025-09-03 8:01 ` kernel test robot
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=8fcea325-ca5f-0abd-34e0-1ac7b092e2fb@gentwo.org \
--to=cl@gentwo.org \
--cc=adamli@os.amperecomputing.com \
--cc=anna-maria@linutronix.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=patches@amperecomputing.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®