On 04/23/2018 09:57 AM, Juri Lelli wrote: > On 23/04/18 15:07, Juri Lelli wrote: >> Hi Waiman, >> >> On 19/04/18 09:46, Waiman Long wrote: >>> v7: >>> - Add a root-only cpuset.cpus.isolated control file for CPU isolation. >>> - Enforce that load_balancing can only be turned off on cpusets with >>> CPUs from the isolated list. >>> - Update sched domain generation to allow cpusets with CPUs only >>> from the isolated CPU list to be in separate root domains. > Guess I'll be adding comments as soon as I stumble on something unclear > (to me :), hope that's OK (shout if I should do it differently). > > The below looked unexpected to me: > > root@debian-kvm:/sys/fs/cgroup# cat g1/cpuset.cpus > 2-3 > root@debian-kvm:/sys/fs/cgroup# cat g1/cpuset.mems > > root@debian-kvm:~# echo $$ > /sys/fs/cgroup/g1/cgroup.threads > root@debian-kvm:/sys/fs/cgroup# cat g1/cgroup.threads > 2312 > > So I can add tasks to groups with no mems? Or is it this only true in my > case with a single mem node? Or maybe it's inherited from root group > (slightly confusing IMHO if that's the case). No mems mean looking up the parents until we find one with non-empty mems. The mems.effective will show you the actual memory nodes used. -Longman -- 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
