On 6/12/22 23:12, Tejun Heo wrote:
Hello,
On Sun, Jun 12, 2022 at 11:02:38PM -0400, Waiman Long wrote:
That is the behavior enforced by setting the CPU_EXCLUSIVE bit in cgroup v1.
I haven't explicitly change it to make it different in cgroup v2. The major
reason is that I don't want change to one cpuset to affect a sibling
partition as it may make the code more complicate to validate if a partition
is valid.
If at all possible, I'd really like to avoid situations where a parent can't
withdraw resources due to something that a descendant does.
No, it doesn't affect parent at all. It just limit whats the siblings
can do due to their mutual constraint. If this is what the confusion is
about, I will try to reword the doc text.
Cheers,
Longman
