Re: [PATCH 2/2] memcg, oom: emit oom report when there is no eligible task

2018-08-21 Thread Johannes Weiner
I sent them in a separate thread. Thanks. On Tue, Aug 21, 2018 at 04:06:12PM +0200, Michal Hocko wrote: > Do you plan to repost these two? They are quite deep in the email thread > so they can easily fall through cracks. > > On Wed 08-08-18 18:17:37, Michal Hocko wrote: > > On Wed 08-08-18 10:45:

Re: [PATCH 2/2] memcg, oom: emit oom report when there is no eligible task

2018-08-21 Thread Michal Hocko
Do you plan to repost these two? They are quite deep in the email thread so they can easily fall through cracks. On Wed 08-08-18 18:17:37, Michal Hocko wrote: > On Wed 08-08-18 10:45:15, Johannes Weiner wrote: [...] > > >From bba01122f739b05a689dbf1eeeb4f0e07affd4e7 Mon Sep 17 00:00:00 2001 > > Fr

Re: [PATCH 2/2] memcg, oom: emit oom report when there is no eligible task

2018-08-08 Thread Michal Hocko
On Wed 08-08-18 10:45:15, Johannes Weiner wrote: > On Wed, Aug 08, 2018 at 09:13:01AM +0200, Michal Hocko wrote: > > From: Michal Hocko > > > > Johannes had doubts that the current WARN in the memcg oom path > > when there is no eligible task is not all that useful because it doesn't > > really g

Re: [PATCH 2/2] memcg, oom: emit oom report when there is no eligible task

2018-08-08 Thread Johannes Weiner
On Wed, Aug 08, 2018 at 09:13:01AM +0200, Michal Hocko wrote: > From: Michal Hocko > > Johannes had doubts that the current WARN in the memcg oom path > when there is no eligible task is not all that useful because it doesn't > really give any useful insight into the memcg state. My original > in

[PATCH 2/2] memcg, oom: emit oom report when there is no eligible task

2018-08-08 Thread Michal Hocko
From: Michal Hocko Johannes had doubts that the current WARN in the memcg oom path when there is no eligible task is not all that useful because it doesn't really give any useful insight into the memcg state. My original intention was to make this lightweight but it is true that seeing a stack tr