Note that when i start up a vivid vm without cgmanager installed, cpuset is still mounted and login sessions get a cpuset cgroup:
ubuntu@v1:~$ dpkg -l | grep cgmanager ubuntu@v1:~$ cat /proc/self/cgroup 10:perf_event:/user.slice/user-1000.slice/session-1.scope 9:freezer:/user.slice/user-1000.slice/session-1.scope 8:memory:/user.slice/user-1000.slice/session-1.scope 7:hugetlb:/user.slice/user-1000.slice/session-1.scope 6:net_cls,net_prio:/user.slice/user-1000.slice/session-1.scope 5:cpu,cpuacct:/user.slice/user-1000.slice/session-1.scope 4:blkio:/user.slice/user-1000.slice/session-1.scope 3:devices:/user.slice/user-1000.slice/session-1.scope 2:cpuset:/user.slice/user-1000.slice/session-1.scope 1:name=systemd:/user.slice/user-1000.slice/session-1.scope
And I do think that's the right thing to do. We simply need the daemon.
@Preeti,
will you be available during the next set of UOS (http://summit.ubuntu.com/uos-1505/) to discuss a good design? Issues include:
. Where to ship the code . How to configure defaults and exceptions . What all needs to be handled (cpusets, memory, hugetlb?)
Note that when i start up a vivid vm without cgmanager installed, cpuset is still mounted and login sessions get a cpuset cgroup:
ubuntu@v1:~$ dpkg -l | grep cgmanager event:/ user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope net_prio: /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope /user.slice/ user-1000. slice/session- 1.scope systemd: /user.slice/ user-1000. slice/session- 1.scope
ubuntu@v1:~$ cat /proc/self/cgroup
10:perf_
9:freezer:
8:memory:
7:hugetlb:
6:net_cls,
5:cpu,cpuacct:
4:blkio:
3:devices:
2:cpuset:
1:name=
And I do think that's the right thing to do. We simply need the daemon.
@Preeti,
will you be available during the next set of UOS (http:// summit. ubuntu. com/uos- 1505/)
to discuss a good design? Issues include:
. Where to ship the code
. How to configure defaults and exceptions
. What all needs to be handled (cpusets, memory, hugetlb?)