Re: [PATCH v2] mm, memcg: introduce memory.events.local

2019-05-20 Thread Johannes Weiner
On Fri, May 17, 2019 at 05:18:18PM -0700, Shakeel Butt wrote: > The memory controller in cgroup v2 exposes memory.events file for each > memcg which shows the number of times events like low, high, max, oom > and oom_kill have happened for the whole tree rooted at that memcg. > Users can also poll

Re: [PATCH v2] mm, memcg: introduce memory.events.local

2019-05-17 Thread Shakeel Butt
On Fri, May 17, 2019 at 5:59 PM Roman Gushchin wrote: > > On Fri, May 17, 2019 at 05:18:18PM -0700, Shakeel Butt wrote: > > The memory controller in cgroup v2 exposes memory.events file for each > > memcg which shows the number of times events like low, high, max, oom > > and oom_kill have happene

Re: [PATCH v2] mm, memcg: introduce memory.events.local

2019-05-17 Thread Roman Gushchin
On Fri, May 17, 2019 at 05:18:18PM -0700, Shakeel Butt wrote: > The memory controller in cgroup v2 exposes memory.events file for each > memcg which shows the number of times events like low, high, max, oom > and oom_kill have happened for the whole tree rooted at that memcg. > Users can also poll

[PATCH v2] mm, memcg: introduce memory.events.local

2019-05-17 Thread Shakeel Butt
The memory controller in cgroup v2 exposes memory.events file for each memcg which shows the number of times events like low, high, max, oom and oom_kill have happened for the whole tree rooted at that memcg. Users can also poll or register notification to monitor the changes in that file. Any even