Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-10-02 Thread Yang Shi
On 10/2/17 4:20 AM, Michal Hocko wrote: On Thu 28-09-17 13:36:57, Tetsuo Handa wrote: On 2017/09/28 6:46, Yang Shi wrote: Changelog v7 —> v8: * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable slabs amount > total user memory. Not only in oom panic path. Holding s

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-10-02 Thread Yang Shi
On 9/30/17 4:00 AM, Tetsuo Handa wrote: Yang Shi wrote: On 9/28/17 1:45 PM, Tetsuo Handa wrote: Yang Shi wrote: On 9/28/17 12:57 PM, Tetsuo Handa wrote: Yang Shi wrote: On 9/27/17 9:36 PM, Tetsuo Handa wrote: On 2017/09/28 6:46, Yang Shi wrote: Changelog v7 -> v8: * Adopted Michal’s sugg

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-10-02 Thread Michal Hocko
On Thu 28-09-17 13:36:57, Tetsuo Handa wrote: > On 2017/09/28 6:46, Yang Shi wrote: > > Changelog v7 —> v8: > > * Adopted Michal’s suggestion to dump unreclaim slab info when > > unreclaimable slabs amount > total user memory. Not only in oom panic path. > > Holding slab_mutex inside dump_unrecla

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-30 Thread Tetsuo Handa
Yang Shi wrote: > On 9/28/17 1:45 PM, Tetsuo Handa wrote: > > Yang Shi wrote: > >> On 9/28/17 12:57 PM, Tetsuo Handa wrote: > >>> Yang Shi wrote: > On 9/27/17 9:36 PM, Tetsuo Handa wrote: > > On 2017/09/28 6:46, Yang Shi wrote: > >> Changelog v7 -> v8: > >> * Adopted Michal’s sugge

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-29 Thread Yang Shi
On 9/28/17 1:45 PM, Tetsuo Handa wrote: Yang Shi wrote: On 9/28/17 12:57 PM, Tetsuo Handa wrote: Yang Shi wrote: On 9/27/17 9:36 PM, Tetsuo Handa wrote: On 2017/09/28 6:46, Yang Shi wrote: Changelog v7 -> v8: * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable slab

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-28 Thread Tetsuo Handa
Yang Shi wrote: > On 9/28/17 12:57 PM, Tetsuo Handa wrote: > > Yang Shi wrote: > >> On 9/27/17 9:36 PM, Tetsuo Handa wrote: > >>> On 2017/09/28 6:46, Yang Shi wrote: > Changelog v7 -> v8: > * Adopted Michal’s suggestion to dump unreclaim slab info when > unreclaimable slabs amount >

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-28 Thread Yang Shi
On 9/28/17 12:57 PM, Tetsuo Handa wrote: Yang Shi wrote: On 9/27/17 9:36 PM, Tetsuo Handa wrote: On 2017/09/28 6:46, Yang Shi wrote: Changelog v7 -> v8: * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable slabs amount > total user memory. Not only in oom panic path.

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-28 Thread Tetsuo Handa
Yang Shi wrote: > On 9/27/17 9:36 PM, Tetsuo Handa wrote: > > On 2017/09/28 6:46, Yang Shi wrote: > >> Changelog v7 -> v8: > >> * Adopted Michal’s suggestion to dump unreclaim slab info when > >> unreclaimable slabs amount > total user memory. Not only in oom panic path. > > > > Holding slab_mute

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-28 Thread Yang Shi
On 9/27/17 9:36 PM, Tetsuo Handa wrote: On 2017/09/28 6:46, Yang Shi wrote: Changelog v7 —> v8: * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable slabs amount > total user memory. Not only in oom panic path. Holding slab_mutex inside dump_unreclaimable_slab() was

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-27 Thread Tetsuo Handa
On 2017/09/28 6:46, Yang Shi wrote: > Changelog v7 —> v8: > * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable > slabs amount > total user memory. Not only in oom panic path. Holding slab_mutex inside dump_unreclaimable_slab() was refrained since V2 because there are

[PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

2017-09-27 Thread Yang Shi
Recently we ran into a oom issue, kernel panic due to no killable process. The dmesg shows huge unreclaimable slabs used almost 100% memory, but kdump doesn't capture vmcore due to some reason. So, it may sound better to capture unreclaimable slab info in oom message when kernel panic to aid tr