Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

From: Juri Lelli
Date: Mon Apr 23 2018 - 09:58:11 EST

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
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

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).