Re: [RFC PATCH v2 6/7] mm, oom: cgroup-aware OOM killer

2017-06-06 Thread Roman Gushchin
On Sun, Jun 04, 2017 at 11:43:33PM +0300, Vladimir Davydov wrote: > On Thu, Jun 01, 2017 at 07:35:14PM +0100, Roman Gushchin wrote: > ... > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > > index f979ac7..855d335 100644 > > --- a/mm/memcontrol.c > > +++ b/mm/memcontrol.c > > @@ -2625,6 +2625,184

Re: [RFC PATCH v2 6/7] mm, oom: cgroup-aware OOM killer

2017-06-04 Thread Vladimir Davydov
On Thu, Jun 01, 2017 at 07:35:14PM +0100, Roman Gushchin wrote: > Traditionally, the OOM killer is operating on a process level. > Under oom conditions, it finds a process with the highest oom score > and kills it. > > This behavior doesn't suit well the system with many running > containers. Ther

[RFC PATCH v2 6/7] mm, oom: cgroup-aware OOM killer

2017-06-01 Thread Roman Gushchin
Traditionally, the OOM killer is operating on a process level. Under oom conditions, it finds a process with the highest oom score and kills it. This behavior doesn't suit well the system with many running containers. There are two main issues: 1) There is no fairness between containers. A small