From: Waiman Long <longman@redhat.com>
To: "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>,
Waiman Long <longman@redhat.com>
Subject: [cgroup/for-6.19 PATCH v3 0/5] cgroup/cpuset: Additional housekeeping check & cleanup
Date: Tue, 4 Nov 2025 23:38:43 -0500 [thread overview]
Message-ID: <20251105043848.382703-1-longman@redhat.com> (raw)
v3: Break out the prstate_housekeeping_conflict() change into 2
new patches with some testing result included.
v2: Update patch 2 to correct some of the checking code and add
prstate_housekeeping_conflict() as suggested by Chen Ridong.
The first two patches are based on the two cpuset patches from the
"timers: Exclude isolated cpus from timer migration" patch series [1]
with some modifications. They add additional nohz_full housekeeping
mask check to ensure that there is at least one common housekeeping
CPU that is not domain and nohz_full isolated.
Patches 3 & 4 fix another housekeeping CPU conflict issue reported by
Chen Ridong.
The last patch is another cleanup patch to simplify the current
partition code.
[1] https://lore.kernel.org/lkml/20251020112802.102451-1-gmonaco@redhat.com/
Gabriele Monaco (1):
cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to
update_isolation_cpumasks()
Waiman Long (4):
cgroup/cpuset: Fail if isolated and nohz_full don't leave any
housekeeping
cgroup/cpuset: Move up prstate_housekeeping_conflict() helper
cgroup/cpuset: Ensure domain isolated CPUs stay in root or isolated
partition
cgroup/cpuset: Globally track isolated_cpus update
kernel/cgroup/cpuset.c | 189 ++++++++++++++++++++++++++++-------------
1 file changed, 130 insertions(+), 59 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-05 4:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 4:38 Waiman Long [this message]
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 1/5] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks() Waiman Long
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 2/5] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Waiman Long
2025-11-05 7:06 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 3/5] cgroup/cpuset: Move up prstate_housekeeping_conflict() helper Waiman Long
2025-11-05 6:18 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 4/5] cgroup/cpuset: Ensure domain isolated CPUs stay in root or isolated partition Waiman Long
2025-11-05 6:29 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 5/5] cgroup/cpuset: Globally track isolated_cpus update Waiman Long
2025-11-05 17:07 ` [PATCH v3 0/5] cgroup/cpuset: Additional housekeeping check & cleanup Tejun Heo
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=20251105043848.382703-1-longman@redhat.com \
--to=longman@redhat.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=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