Re: [PATCH v2] oom, oom_reaper: do not enqueue same task twice

2019-01-27 Thread Michal Hocko
On Sun 27-01-19 19:56:06, Tetsuo Handa wrote: > On 2019/01/27 17:37, Michal Hocko wrote: > > Thanks for the analysis and the patch. This should work, I believe but > > I am not really thrilled to overload the meaning of the MMF_UNSTABLE. > > The flag is meant to signal accessing address space is no

Re: [PATCH v2] oom, oom_reaper: do not enqueue same task twice

2019-01-27 Thread Tetsuo Handa
On 2019/01/27 17:37, Michal Hocko wrote: > Thanks for the analysis and the patch. This should work, I believe but > I am not really thrilled to overload the meaning of the MMF_UNSTABLE. > The flag is meant to signal accessing address space is not stable and it > is not aimed to synchronize oom reap

Re: [PATCH v2] oom, oom_reaper: do not enqueue same task twice

2019-01-27 Thread Michal Hocko
On Sat 26-01-19 22:10:52, Tetsuo Handa wrote: [...] > >From 9c9e935fc038342c48461aabca666f1b544e32b1 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Sat, 26 Jan 2019 21:57:25 +0900 > Subject: [PATCH v2] oom, oom_reaper: do not enqueue same task twice > > Arkadiusz r

[PATCH v2] oom, oom_reaper: do not enqueue same task twice

2019-01-26 Thread Tetsuo Handa
etsuo Handa Date: Sat, 26 Jan 2019 21:57:25 +0900 Subject: [PATCH v2] oom, oom_reaper: do not enqueue same task twice Arkadiusz reported that enabling memcg's group oom killing causes strange memcg statistics where there is no task in a memcg despite the number of tasks in that mem