Re: [PATCH v10 2/2] Refactor part of the oom report in dump_header

2018-06-28 Thread Michal Hocko
On Wed 27-06-18 19:10:41, Andrew Morton wrote: > On Sat, 23 Jun 2018 22:12:51 +0800 ufo19890...@gmail.com wrote: > > > From: yuzhoujian > > > > The current system wide oom report prints information about the victim > > and the allocation context and restrictions. It, however, doesn't > > provide

Re: [PATCH v10 2/2] Refactor part of the oom report in dump_header

2018-06-27 Thread Andrew Morton
On Sat, 23 Jun 2018 22:12:51 +0800 ufo19890...@gmail.com wrote: > From: yuzhoujian > > The current system wide oom report prints information about the victim > and the allocation context and restrictions. It, however, doesn't > provide any information about memory cgroup the victim belongs to. T

[PATCH v10 2/2] Refactor part of the oom report in dump_header

2018-06-23 Thread ufo19890607
From: yuzhoujian The current system wide oom report prints information about the victim and the allocation context and restrictions. It, however, doesn't provide any information about memory cgroup the victim belongs to. This information can be interesting for container users because they can fin