Re: [RFC PATCH v2 1/3] cgroup/pids: Separate semantics of pids.events related to pids.max
From: Tejun Heo
Date: Wed Feb 12 2020 - 18:03:11 EST
On Wed, Feb 05, 2020 at 02:44:24PM +0100, Michal Koutný wrote:
> 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.
>
> Let's introduce new events:
> max
> The number of times the limit of the cgroup was hit.
>
> max.imposed
> The number of times fork failed in the cgroup because of self
> or ancestor limit.
Can you please follow the same convention as memory.events and
memory.events.local?
Thanks.
--
tejun