Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-16 Thread Tetsuo Handa
On 2018/11/15 20:36, Michal Hocko wrote: > On Thu 15-11-18 18:54:15, Tetsuo Handa wrote: > > On 2018/11/14 19:16, Michal Hocko wrote: > > > On Wed 14-11-18 18:46:13, Tetsuo Handa wrote: > > > [...] > > > > There is always an invisible lock called "scheduling priority". You > > > > can't > > > > le

Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-15 Thread Michal Hocko
On Thu 15-11-18 18:54:15, Tetsuo Handa wrote: > On 2018/11/14 19:16, Michal Hocko wrote: > > On Wed 14-11-18 18:46:13, Tetsuo Handa wrote: > > [...] > > > There is always an invisible lock called "scheduling priority". You can't > > > leave the MMF_OOM_SKIP to the exit path. Your approach is not re

Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-15 Thread Tetsuo Handa
On 2018/11/14 19:16, Michal Hocko wrote: > On Wed 14-11-18 18:46:13, Tetsuo Handa wrote: > [...] > > There is always an invisible lock called "scheduling priority". You can't > > leave the MMF_OOM_SKIP to the exit path. Your approach is not ready for > > handling the worst case. > > And that probl

Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-14 Thread Michal Hocko
On Wed 14-11-18 18:46:13, Tetsuo Handa wrote: [...] > There is always an invisible lock called "scheduling priority". You can't > leave the MMF_OOM_SKIP to the exit path. Your approach is not ready for > handling the worst case. And that problem is all over the memory reclaim. You can get starved

Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-14 Thread Tetsuo Handa
On 2018/11/08 18:32, Michal Hocko wrote: > On Thu 25-10-18 10:24:00, Michal Hocko wrote: >> The previous version of this RFC has been posted here [1]. I have fixed >> few issues spotted during the review and by 0day bot. I have also reworked >> patch 2 to be ratio rather than an absolute number bas

Re: [RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-11-08 Thread Michal Hocko
On Thu 25-10-18 10:24:00, Michal Hocko wrote: > The previous version of this RFC has been posted here [1]. I have fixed > few issues spotted during the review and by 0day bot. I have also reworked > patch 2 to be ratio rather than an absolute number based. > > With this series applied the locking

[RFC PATCH v2 0/3] oom: rework oom_reaper vs. exit_mmap handoff

2018-10-25 Thread Michal Hocko
The previous version of this RFC has been posted here [1]. I have fixed few issues spotted during the review and by 0day bot. I have also reworked patch 2 to be ratio rather than an absolute number based. With this series applied the locking protocol between the oom_reaper and the exit path is as