Re: [PATCH v4] Print the memcg's name when system-wide OOM happened

2018-05-30 Thread Michal Hocko
On Wed 30-05-18 13:42:56, Andrew Morton wrote: > On Mon, 21 May 2018 03:39:46 +0100 ufo19890607 wrote: > > > From: yuzhoujian > > > > The dump_header does not print the memcg's name when the system > > oom happened. So users cannot locate the certain container which > > contains the task that h

Re: [PATCH v4] Print the memcg's name when system-wide OOM happened

2018-05-30 Thread Andrew Morton
On Mon, 21 May 2018 03:39:46 +0100 ufo19890607 wrote: > From: yuzhoujian > > The dump_header does not print the memcg's name when the system > oom happened. So users cannot locate the certain container which > contains the task that has been killed by the oom killer. > > System oom report will

Re: [PATCH v4] Print the memcg's name when system-wide OOM happened

2018-05-22 Thread Michal Hocko
On Mon 21-05-18 03:39:46, ufo19890607 wrote: > From: yuzhoujian > > The dump_header does not print the memcg's name when the system > oom happened. So users cannot locate the certain container which > contains the task that has been killed by the oom killer. > > System oom report will print the

[PATCH v4] Print the memcg's name when system-wide OOM happened

2018-05-20 Thread ufo19890607
From: yuzhoujian The dump_header does not print the memcg's name when the system oom happened. So users cannot locate the certain container which contains the task that has been killed by the oom killer. System oom report will print the memcg's name after this patch, so users can get the memcg's