From: Waiman Long <llong@redhat.com>
To: "Chen Ridong" <chenridong@huaweicloud.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 2/3] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping
Date: Mon, 3 Nov 2025 16:22:18 -0500 [thread overview]
Message-ID: <8bf57eed-0e07-4102-900e-e63c1110815c@redhat.com> (raw)
In-Reply-To: <05281aa9-57c4-42c7-a17c-009d6b22943b@huaweicloud.com>
On 11/2/25 10:53 PM, Chen Ridong wrote:
>
>
>> +
>> /*
>> * Change the parent's effective_cpus & effective_xcpus (top cpuset
>> * only).
>> @@ -2994,7 +3055,11 @@ static int update_prstate(struct cpuset *cs, int new_prs)
>> * A change in load balance state only, no change in cpumasks.
>> * Need to update isolated_cpus.
>> */
>> - isolcpus_updated = true;
>> + if ((new_prs == PRS_ISOLATED) &&
>> + !isolated_cpus_can_update(cs->effective_xcpus, NULL))
>> + err = PERR_HKEEPING;
>> + else
>> + isolcpus_updated = true;
>> } else {
>> /*
>> * Switching back to member is always allowed even if it
> This is an issue I am trying to fix, the prstate_housekeeping_conflict check is necessary.
>
> https://lore.kernel.org/cgroups/20251025064844.495525-2-chenridong@huaweicloud.com/
>
You are right. We should add prstate_housekeeping_conflict() check here.
BTW, I found some issues when I looked further at the patch. So I am
going to rewrite part of it and will send out a v2 after some testing.
Cheers,
Longman
next prev parent reply other threads:[~2025-11-03 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 1:34 [cgroup/for-6.19 PATCH 0/3] cgroup/cpuset: Additional housekeeping check & cleanup Waiman Long
2025-11-03 1:34 ` [cgroup/for-6.19 PATCH 1/3] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks() Waiman Long
2025-11-03 2:56 ` Chen Ridong
2025-11-03 1:34 ` [cgroup/for-6.19 PATCH 2/3] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Waiman Long
2025-11-03 2:55 ` Chen Ridong
2025-11-03 3:12 ` Waiman Long
2025-11-03 3:26 ` Chen Ridong
2025-11-03 3:47 ` Chen Ridong
2025-11-03 3:59 ` Chen Ridong
2025-11-03 3:53 ` Chen Ridong
2025-11-03 21:22 ` Waiman Long [this message]
2025-11-03 1:34 ` [cgroup/for-6.19 PATCH 3/3] cgroup/cpuset: Globally track isolated_cpus update Waiman Long
2025-11-03 6:46 ` Chen Ridong
2025-11-03 21:17 ` Waiman Long
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=8bf57eed-0e07-4102-900e-e63c1110815c@redhat.com \
--to=llong@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=frederic@kernel.org \
--cc=gmonaco@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--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®