Messages in this thread | | | Date | Mon, 10 Jul 2023 11:30:12 -1000 | From | Tejun Heo <> | Subject | Re: [PATCH v4 8/9] cgroup/cpuset: Documentation update for partition |
| |
Hello,
On Tue, Jun 27, 2023 at 10:35:07AM -0400, Waiman Long wrote: ... > + There are two types of partitions - local and remote. A local > + partition is one whose parent cgroup is also a valid partition > + root. A remote partition is one whose parent cgroup is not a > + valid partition root itself. Writing to "cpuset.cpus.exclusive" > + is not mandatory for the creation of a local partition as its > + "cpuset.cpus.exclusive" file will be filled in automatically if > + it is not set. The automaticaly set value will be based on its > + "cpuset.cpus" value. Writing the proper "cpuset.cpus.exclusive" > + values down the cgroup hierarchy is mandatory for the creation > + of a remote partition.
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?
Thanks.
-- tejun
| |