Re: [PATCH cgroup/for-6.20 v4 4/5] cgroup/cpuset: Don't invalidate sibling partitions on cpuset.cpus conflict

[Waiman Long <llong@redhat.com>]

On 1/12/26 5:51 AM, Michal Koutný wrote:
> On Sun, Jan 11, 2026 at 11:08:55PM -0500, Waiman Long <longman@redhat.com> wrote:
>> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> ...
>> @@ -2632,6 +2641,9 @@ Cpuset Interface Files
>>   
>>   	The root cgroup is always a partition root and its state cannot
>>   	be changed.  All other non-root cgroups start out as "member".
>> +	Even though the "cpuset.cpus.exclusive*" control files are not
>> +	present in the root cgroup, they are implicitly the same as
>> +	"cpuset.cpus".
> cpuset.cpus.effective (that one is on root cpuset cg)
>
> (This was likely lost among my v2 comments.)

Sorry, I might have missed this comment of yours. The 
"cpuset.cpus.exclusive" file lists all the CPUs that can be granted to 
its children as exclusive CPUs. The cgroup root is an implicit partition 
root where all its CPUs can be granted to its children whether they are 
online or offline. "cpuset.cpus.effective" OTOH ignores the offline CPUs 
as well as exclusive CPUs that have been passed down to existing 
descendant partition roots so it may differ from the implicit 
"cpuset.cpus.exclusive".

Cheers,
Longman