From: Qiliang Yuan <realwujing@gmail.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 01,03,07,08,09/12] DHM Architecture and Cpuset Integration
Date: Mon, 20 Apr 2026 17:21:23 +0800 [thread overview]
Message-ID: <20260420092123.240974-1-realwujing@gmail.com> (raw)
In-Reply-To: <20260415100246.654321-1-frederic@kernel.org>
I agree that extending the existing "isolated" partition in cpusets is a
more integrated approach. For v3, I will explore a new mode for the
cpuset.cpus.partition interface to support dynamic nohz_full/nocb transitions.
On Wed, 15 Apr 2026 12:39:09 +0200, Frederic Weisbecker wrote:
> We plan to assume that the CPU is offline while updating HK_TYPE_KERNEL_NOISE
> through cpusets. So you shouldn't need to care about offlining here.
The CPU offline logic in the RCU reconfiguration will be streamlined,
relying on the state managed by the cpuset/hotplug core.
On Wed, 15 Apr 2026 12:50:03 +0200, Frederic Weisbecker wrote:
> Unbound workqueues and kthreads are already handled by cpuset isolated
> partitions.
Affinity management for workqueues and domains will be removed from the
DHM patches, as these are indeed already addressed by the isolated
partition logic.
Best regards,
Qiliang
---
To: Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v2 01/12] sched/isolation: Use cases for fine-grained isolation
Date: Mon, 20 Apr 2026 16:15:00 +0800
Hi Waiman,
parent reply other threads:[~2026-04-20 9:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260415100246.654321-1-frederic@kernel.org>]
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=20260420092123.240974-1-realwujing@gmail.com \
--to=realwujing@gmail.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