On 7/10/23 20:42, Tejun Heo wrote:
Hello,
On Mon, Jul 10, 2023 at 08:21:43PM -0400, Waiman Long wrote:
Wouldn't a partition root's cpus.exclusive always contain all of the CPUs in
its cpus? Would it make sense for cpus.exclusive to be different from .cpus?
In auto-filled case, it should be the same as cpuset.cpus. I will clarify
that in the documentation. Thanks for catching that.
When the user writes something to the file, what would it mena if the
content differs from the cgroup's cpuset.cpus?
For local partition, it doesn't make sense to have a
cpust.cpus.exclusive that is not the same as cpuset.cpus as it
artificially reduce the set of CPUs that can be used in a partition. In
the case of a remote partition, the ancestor cgroups of a remote
partition should have cpuset.cpus.exclusive smaller than cpuset.cpus so
that when the remote partition is enabled, there are still CPUs left to
be used by those cgroups. In essence, the cpuset.cpus.exclusive
represents the CPUs that may not be usable anymore if they are taken by
a remote partition downstream.
Cheers,
Longman
