Re: [PATCH] cgroup/cpuset: Make cpuset.cpus.effective independent of cpuset.cpus

Waiman Long
2024-03-26T15:15:02Z

On 3/25/24 16:12, Tejun Heo wrote:
> On Thu, Mar 21, 2024 at 10:39:45PM +0100, Petr Malat wrote:
>> Requiring cpuset.cpus.effective to be a subset of cpuset.cpus makes it
>> hard to use as one is forced to configure cpuset.cpus of current and all
>> ancestor cgroups, which requires a knowledge about all other units
>> sharing the same cgroup subtree. Also, it doesn't allow using empty
>> cpuset.cpus.
>>
>> Do not require cpuset.cpus.effective to be a subset of cpuset.cpus and
>> create remote cgroup only if cpuset.cpus is empty, to make it easier for
>> the user to control which cgroup is being created.
>>
>> Signed-off-by: Petr Malat <oss@malat.biz>
> Waiman, what do you think?

I think it is possible to make cpuset.cpus.exclusive independent of
cpuset.cpus. There are probably more places that need to be changed
including the cgroup-v2.rst file.

Cheers,
Longman

>
> Thanks.
>