[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251105043848.382703-1-longman@redhat.com>
Date: Tue, 4 Nov 2025 23:38:43 -0500
From: Waiman Long <longman@...hat.com>
To: Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Koutný <mkoutny@...e.com>
Cc: cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org,
Chen Ridong <chenridong@...wei.com>,
Gabriele Monaco <gmonaco@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Waiman Long <longman@...hat.com>
Subject: [cgroup/for-6.19 PATCH v3 0/5] cgroup/cpuset: Additional housekeeping check & cleanup
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
Powered by blists - more mailing lists