[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d1b9c9e-a63b-4385-b706-0eee73688343@redhat.com>
Date: Thu, 3 Apr 2025 09:48:44 -0400
From: Waiman Long <llong@...hat.com>
To: Michal Koutný <mkoutny@...e.com>
Cc: Tejun Heo <tj@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
Shuah Khan <shuah@...nel.org>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 05/10] cgroup/cpuset: Don't allow creation of local
partition over a remote one
On 4/3/25 9:33 AM, Michal Koutný wrote:
> On Sun, Mar 30, 2025 at 05:52:43PM -0400, Waiman Long <longman@...hat.com> wrote:
>> Currently, we don't allow the creation of a remote partition underneath
>> another local or remote partition. However, it is currently possible to
>> create a new local partition with an existing remote partition underneath
>> it if top_cpuset is the parent. However, the current cpuset code does
>> not set the effective exclusive CPUs correctly to account for those
>> that are taken by the remote partition.
> That sounds like
> Fixes: 181c8e091aae1 ("cgroup/cpuset: Introduce remote partition")
>
> (but it's merge, so next time :-)
Commit ee8dde0cd2ce ("cpuset: Add new v2 cpuset.sched.partition flag")
is actually the first commit that introduces the concept of cpuset
partition which is basically the local partition that I am referring to
now. It is that commit that did the partition cleanup in
cpuset_css_offline() which is now being moved to the new
cpuset_css_killed() callback function.
Thanks,
Longman
Powered by blists - more mailing lists