[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <uogjuuvcu7vsazm53xztqg2tiqeeestcfxwjyopeapoi3nji3d@7dsxwvynzcah>
Date: Mon, 12 Jan 2026 16:08:30 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Waiman Long <llong@...hat.com>
Cc: Tejun Heo <tj@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>, Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org,
Sun Shaojie <sunshaojie@...inos.cn>, Chen Ridong <chenridong@...weicloud.com>,
Chen Ridong <chenridong@...wei.com>
Subject: Re: [PATCH cgroup/for-6.20 v4 4/5] cgroup/cpuset: Don't invalidate
sibling partitions on cpuset.cpus conflict
On Mon, Jan 12, 2026 at 09:51:28AM -0500, Waiman Long <llong@...hat.com> wrote:
> 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".
Howewer, there's no "cpuset.cpus" configurable nor visible on the root
cgroup. So possibly drop this hunk altogether for simplicity?
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (266 bytes)
Powered by blists - more mailing lists