Thanks - Martin - tested that with the mainline kernel, and it did indeed give me a pids cgroup:
ubuntu@pitti:~$ cat /proc/self/cgroup 11:hugetlb:/user.slice/user-1000.slice/session-2.scope 10:blkio:/user.slice/user-1000.slice/session-2.scope 9:devices:/user.slice/user-1000.slice/session-2.scope 8:pids:/user.slice/user-1000.slice/session-2.scope 7:memory:/user.slice/user-1000.slice/session-2.scope 6:perf_event:/user.slice/user-1000.slice/session-2.scope 5:cpuset:/user.slice/user-1000.slice/session-2.scope 4:net_cls,net_prio:/user.slice/user-1000.slice/session-2.scope 3:freezer:/user.slice/user-1000.slice/session-2.scope 2:cpu,cpuacct:/user.slice/user-1000.slice/session-2.scope 1:name=systemd:/user.slice/user-1000.slice/session-2.scope
Thanks - Martin - tested that with the mainline kernel, and it did indeed
give me a pids cgroup:
ubuntu@pitti:~$ cat /proc/self/cgroup /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope event:/ user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope net_prio: /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope /user.slice/ user-1000. slice/session- 2.scope systemd: /user.slice/ user-1000. slice/session- 2.scope
11:hugetlb:
10:blkio:
9:devices:
8:pids:
7:memory:
6:perf_
5:cpuset:
4:net_cls,
3:freezer:
2:cpu,cpuacct:
1:name=