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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 21, 2024 at 10:39:45PM +0100, Petr Malat 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.
> 
> Do not require cpuset.cpus.effective to be a subset of cpuset.cpus and
> create remote cgroup only if cpuset.cpus is empty, to make it easier for
> the user to control which cgroup is being created.
> 
> Signed-off-by: Petr Malat <oss@xxxxxxxxx>

Waiman, what do you think?

Thanks.

-- 
tejun




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux