[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d7ddb5a-0d0b-3f2e-e049-900360e95fc6@redhat.com>
Date: Mon, 13 Jun 2022 09:18:55 -0400
From: Waiman Long <longman@...hat.com>
To: Tejun Heo <tj@...nel.org>
Cc: Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>,
Shuah Khan <shuah@...nel.org>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kselftest@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <guro@...com>, Phil Auld <pauld@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Michal Koutný <mkoutny@...e.com>
Subject: Re: [PATCH v11 7/8] cgroup/cpuset: Update description of
cpuset.cpus.partition in cgroup-v2.rst
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
Powered by blists - more mailing lists