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

Michal Koutný
2024-04-02T17:05:00Z

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Hello.

On Thu, Mar 21, 2024 at 10:39:45PM +0100, Petr Malat <oss@malat.biz> 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.
^^^^^^^^^^^^^^^^^
_this_ is what cpuset has been missing IMO

I think cpuset v2 should allow empty value in cpuset.cpus (not only
default but also as a reset (to the default)) which would implicitely
mean using whatever CPUs were passed from parent(s).

Does that make sense to you too?

Thus the patch(es) seems to need to be extended to handle a case when
empty cpuset.cpus is assigned but no cpuset.cpus.exclusive are
specified neither.

Thanks,
Michal

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]