From: Chen Ridong <chenridong@huaweicloud.com>
To: "Waiman Long" <llong@redhat.com>, "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Chen Ridong <chenridong@huawei.com>,
Gabriele Monaco <gmonaco@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [cgroup/for-6.19 PATCH v2 2/3] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping
Date: Tue, 4 Nov 2025 15:26:06 +0800 [thread overview]
Message-ID: <30cc7ea0-aaae-46f4-b31b-9d30639b8cea@huaweicloud.com> (raw)
In-Reply-To: <d6fd5e9c-d302-43db-ac89-7b09ab0770be@redhat.com>
On 2025/11/4 12:10, Waiman Long wrote:
> I do think your patch series will make that simpler. You can certainly update your patch series to
> include that additional check into validate_partition().
Okay. After you have reviewed the patches, I will prepare a revision that incorporates the
additional check.
--
Best regards,
Ridong
next prev parent reply other threads:[~2025-11-04 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 1:30 [cgroup/for-6.19 PATCH v2 0/3] cgroup/cpuset: Additional housekeeping check & cleanup Waiman Long
2025-11-04 1:30 ` [cgroup/for-6.19 PATCH v2 1/3] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks() Waiman Long
2025-11-04 1:30 ` [cgroup/for-6.19 PATCH v2 2/3] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Waiman Long
2025-11-04 2:19 ` Chen Ridong
2025-11-04 4:10 ` Waiman Long
2025-11-04 7:26 ` Chen Ridong [this message]
2025-11-04 1:30 ` [cgroup/for-6.19 PATCH v2 3/3] cgroup/cpuset: Globally track isolated_cpus update Waiman Long
2025-11-04 2:21 ` Chen Ridong
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=30cc7ea0-aaae-46f4-b31b-9d30639b8cea@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=frederic@kernel.org \
--cc=gmonaco@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=mkoutny@suse.com \
--cc=tj@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
all inboxes | Powered by JetHome®