From: "Yang Shi" <yang.s@alibaba-inc.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory
Date: Thu, 05 Oct 2017 02:08:48 +0800 [thread overview]
Message-ID: <4b668145-a81d-6f46-0569-b0adb76788d8@alibaba-inc.com> (raw)
In-Reply-To: <20171004142736.u4z7zdar6g7bqgrj@dhcp22.suse.cz>
On 10/4/17 7:27 AM, Michal Hocko wrote:
> On Wed 04-10-17 02:06:17, Yang Shi wrote:
>> +static bool is_dump_unreclaim_slabs(void)
>> +{
>> + unsigned long nr_lru;
>> +
>> + nr_lru = global_node_page_state(NR_ACTIVE_ANON) +
>> + global_node_page_state(NR_INACTIVE_ANON) +
>> + global_node_page_state(NR_ACTIVE_FILE) +
>> + global_node_page_state(NR_INACTIVE_FILE) +
>> + global_node_page_state(NR_ISOLATED_ANON) +
>> + global_node_page_state(NR_ISOLATED_FILE) +
>> + global_node_page_state(NR_UNEVICTABLE);
>> +
>> + return (global_node_page_state(NR_SLAB_UNRECLAIMABLE) > nr_lru);
>> +}
>
> I am sorry I haven't pointed this earlier (I was following only half
> way) but this should really be memcg aware. You are checking only global
> counters. I do not think it is an absolute must to provide per-memcg
> data but you should at least check !is_memcg_oom(oc).
BTW, I saw there is already such check in dump_header that looks like
the below code:
if (oc->memcg)
mem_cgroup_print_oom_info(oc->memcg, p);
else
show_mem(SHOW_MEM_FILTER_NODES, oc->nodemask);
I'm supposed it'd better to replace "oc->memcg" to "is_memcg_oom(oc)"
since they do the same check and "is_memcg_oom" interface sounds preferable.
Then I'm going to move unreclaimable slabs dump to the "else" block.
Yang
>
> [...]
>> +void dump_unreclaimable_slab(void)
>> +{
>> + struct kmem_cache *s, *s2;
>> + struct slabinfo sinfo;
>> +
>> + pr_info("Unreclaimable slab info:\n");
>> + pr_info("Name Used Total\n");
>> +
>> + /*
>> + * Here acquiring slab_mutex is risky since we don't prefer to get
>> + * sleep in oom path. But, without mutex hold, it may introduce a
>> + * risk of crash.
>> + * Use mutex_trylock to protect the list traverse, dump nothing
>> + * without acquiring the mutex.
>> + */
>> + if (!mutex_trylock(&slab_mutex))
>> + return;
>
> I would move the trylock up so that we do not get empty and confusing
> Unreclaimable slab info: and add a note that we are not dumping anything
> due to lock contention
> pr_warn("excessive unreclaimable slab memory but cannot dump stats to give you more details\n");
>
> Other than that this looks sensible to me.
>
>> + list_for_each_entry_safe(s, s2, &slab_caches, list) {
>> + if (!is_root_cache(s) || (s->flags & SLAB_RECLAIM_ACCOUNT))
>> + continue;
>> +
>> + memset(&sinfo, 0, sizeof(sinfo));
>> + get_slabinfo(s, &sinfo);
>> +
>> + if (sinfo.num_objs > 0)
>> + pr_info("%-17s %10luKB %10luKB\n", cache_name(s),
>> + (sinfo.active_objs * s->size) / 1024,
>> + (sinfo.num_objs * s->size) / 1024);
>> + }
>> + mutex_unlock(&slab_mutex);
>> +}
>> +
>> #if defined(CONFIG_MEMCG) && !defined(CONFIG_SLOB)
>> void *memcg_slab_start(struct seq_file *m, loff_t *pos)
>> {
>> --
>> 1.8.3.1
>
--
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-10-04 18:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 18:06 [PATCH 0/3 v8] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-03 18:06 ` [PATCH 1/3] tools: slabinfo: add "-U" option to show unreclaimable slabs only Yang Shi
2017-10-03 18:06 ` [PATCH 2/3] mm: slabinfo: dump CONFIG_SLABINFO Yang Shi
2017-10-03 18:06 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-04 14:27 ` Michal Hocko
2017-10-04 17:37 ` Yang Shi
2017-10-04 18:08 ` Yang Shi [this message]
2017-10-05 7:57 ` Michal Hocko
2017-10-03 18:10 ` [PATCH 0/3 v8] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-04 21:29 [PATCH 0/3 v10] " Yang Shi
2017-10-04 21:29 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-06 9:37 ` Michal Hocko
2017-10-06 16:37 ` Yang Shi
2017-10-09 6:33 ` Michal Hocko
2017-10-09 6:36 ` Michal Hocko
2017-10-09 16:44 ` Yang Shi
2017-10-09 18:53 ` Yang Shi
2017-10-09 21:00 ` Yang Shi
2017-10-07 10:10 ` kbuild test robot
2017-10-07 13:05 ` kbuild test robot
2017-10-10 17:25 [PATCH 0/3 v11] oom: capture unreclaimable slab info in oom message Yang Shi
2017-10-10 17:25 ` [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory Yang Shi
2017-10-17 0:15 ` David Rientjes
2017-10-17 7:44 ` Michal Hocko
2017-10-17 20:59 ` David Rientjes
2017-10-17 21:40 ` Yang Shi
2017-10-17 21:50 ` David Rientjes
2017-10-17 22:20 ` Yang Shi
2017-10-17 22:39 ` David Rientjes
2017-10-18 19:09 ` Yang Shi
2017-10-19 7:28 ` Michal Hocko
2017-10-19 23:12 ` 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=4b668145-a81d-6f46-0569-b0adb76788d8@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