From: "Yang Shi" <yang.s@alibaba-inc.com>
To: Christopher Lameter <cl@linux.com>
Cc: penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, mhocko@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mm: oom: show unreclaimable slab info when kernel panic
Date: Thu, 28 Sep 2017 01:21:27 +0800 [thread overview]
Message-ID: <c7459b93-4197-6968-6735-a97a06325d04@alibaba-inc.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709270211010.30111@nuc-kabylake>
On 9/27/17 12:14 AM, Christopher Lameter wrote:
> On Wed, 27 Sep 2017, Yang Shi wrote:
>
>> Print out unreclaimable slab info (used size and total size) which
>> actual memory usage is not zero (num_objs * size != 0) when:
>> - unreclaimable slabs : all user memory > unreclaim_slabs_oom_ratio
>> - panic_on_oom is set or no killable process
>
> Ok. I like this much more than the earlier releases.
>
>> diff --git a/mm/slab.h b/mm/slab.h
>> index 0733628..b0496d1 100644
>> --- a/mm/slab.h
>> +++ b/mm/slab.h
>> @@ -505,6 +505,14 @@ static inline struct kmem_cache_node *get_node(struct kmem_cache *s, int node)
>> void memcg_slab_stop(struct seq_file *m, void *p);
>> int memcg_slab_show(struct seq_file *m, void *p);
>>
>> +#ifdef CONFIG_SLABINFO
>> +void dump_unreclaimable_slab(void);
>> +#else
>> +static inline void dump_unreclaimable_slab(void)
>> +{
>> +}
>> +#endif
>
> CONFIG_SLABINFO? How does this relate to the oom info? /proc/slabinfo
> support is optional. Oom info could be included even if CONFIG_SLABINFO
> goes away. Remove the #ifdef?
Because we want to dump the unreclaimable slab info in oom info.
Thanks,
Yang
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-09-27 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 0:53 [PATCH 0/3 v7] oom: capture unreclaimable slab info in oom message " Yang Shi
2017-09-27 0:53 ` [PATCH 1/3] tools: slabinfo: add "-U" option to show unreclaimable slabs only Yang Shi
2017-09-27 0:53 ` [PATCH 2/3] mm: oom: show unreclaimable slab info when kernel panic Yang Shi
2017-09-27 7:14 ` Christopher Lameter
2017-09-27 17:21 ` Yang Shi [this message]
2017-09-27 21:59 ` Christopher Lameter
2017-09-27 22:11 ` Yang Shi
2017-10-01 6:43 ` Christopher Lameter
2017-10-02 15:44 ` Yang Shi
2017-09-27 10:45 ` Michal Hocko
2017-09-27 17:25 ` Yang Shi
2017-10-02 7:26 ` Michal Hocko
2017-10-02 15:44 ` Yang Shi
2017-09-27 0:53 ` [PATCH 3/3] doc: add description for unreclaim_slabs_oom_ratio Yang Shi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7459b93-4197-6968-6735-a97a06325d04@alibaba-inc.com \
--to=yang.s@alibaba-inc.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox