Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-07 Thread Roman Gushchin
On Wed, Dec 06, 2017 at 05:24:13PM -0800, Andrew Morton wrote: > > As a result of the "stalled MM patches" discussion I've dropped these > three patches: > > mm,oom: move last second allocation to inside the OOM killer > mm,oom: use ALLOC_OOM for OOM victim's last second allocation > mm,oom:

Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-07 Thread Roman Gushchin
On Wed, Dec 06, 2017 at 05:24:13PM -0800, Andrew Morton wrote: > > As a result of the "stalled MM patches" discussion I've dropped these > three patches: > > mm,oom: move last second allocation to inside the OOM killer > mm,oom: use ALLOC_OOM for OOM victim's last second allocation > mm,oom:

Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-06 Thread Andrew Morton
As a result of the "stalled MM patches" discussion I've dropped these three patches: mm,oom: move last second allocation to inside the OOM killer mm,oom: use ALLOC_OOM for OOM victim's last second allocation mm,oom: remove oom_lock serialization from the OOM reaper and I had to rework this

Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-06 Thread Andrew Morton
As a result of the "stalled MM patches" discussion I've dropped these three patches: mm,oom: move last second allocation to inside the OOM killer mm,oom: use ALLOC_OOM for OOM victim's last second allocation mm,oom: remove oom_lock serialization from the OOM reaper and I had to rework this

Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-01 Thread Michal Hocko
On Thu 30-11-17 15:28:20, 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: > > 1) There is no

Re: [PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-12-01 Thread Michal Hocko
On Thu 30-11-17 15:28:20, 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: > > 1) There is no

[PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-11-30 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: 1) There is no fairness between containers. A small container with few large

[PATCH v13 3/7] mm, oom: cgroup-aware OOM killer

2017-11-30 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: 1) There is no fairness between containers. A small container with few large