73e75e6fc3
Currently, when pids.max limit is breached in the hierarchy, the event is counted and reported in the cgroup where the forking task resides. This decouples the limit and the notification caused by the limit making it hard to detect when the actual limit was effected. Redefine the pids.events:max as: the number of times the limit of the cgroup was hit. (Implementation differentiates also "forkfail" event but this is currently not exposed as it would better fit into pids.stat. It also differs from pids.events:max only when pids.max is configured on non-leaf cgroups.) Since it changes semantics of the original "max" event, introduce this change only in the v2 API of the controller and add a cgroup2 mount option to revert to the legacy behavior. Signed-off-by: Michal Koutný <mkoutny@suse.com> Signed-off-by: Tejun Heo <tj@kernel.org> |
||
|---|---|---|
| .. | ||
| blkio-controller.rst | ||
| cgroups.rst | ||
| cpuacct.rst | ||
| cpusets.rst | ||
| devices.rst | ||
| freezer-subsystem.rst | ||
| hugetlb.rst | ||
| index.rst | ||
| memcg_test.rst | ||
| memory.rst | ||
| misc.rst | ||
| net_cls.rst | ||
| net_prio.rst | ||
| pids.rst | ||
| rdma.rst | ||