On 19/04/18 09:47, Waiman Long wrote: [...] > + cpuset.cpus.isolated > + A read-write multiple values file which exists on root cgroup > + only. > + > + It lists the CPUs that have been withdrawn from the root cgroup > + for load balancing. These CPUs can still be allocated to child > + cpusets with load balancing enabled, if necessary. > + > + If a child cpuset contains only an exclusive set of CPUs that are > + a subset of the isolated CPUs and with load balancing enabled, > + these CPUs will be load balanced on a separate root domain from > + the one in the root cgroup. > + > + Just putting the CPUs into "cpuset.cpus.isolated" will be > + enough to disable load balancing on those CPUs as long as they > + do not appear in a child cpuset with load balancing enabled. Tasks that were on those CPUs when they got isolated will stay there (unless forcibly moved somewhere else). They will also "automatically" belong to default root domain (or potentially to a new root domain created for a group using those CPUs). Both things are maybe unavoidable (as discussed in previous versions some tasks cannot be migrated at all), but such "side effects" should probably be documented. What do you think? -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
