From: Christopher Lameter <cl@linux.com>
To: Yang Shi <yang.s@alibaba-inc.com>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <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: Sun, 1 Oct 2017 01:43:45 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1710010142420.25658@nuc-kabylake> (raw)
In-Reply-To: <b023b5f4-84b5-1686-7b15-c9a3a439b8be@alibaba-inc.com>
On Thu, 28 Sep 2017, Yang Shi wrote:
> > CONFIG_SLABINFO and /proc/slabinfo have nothing to do with the
> > unreclaimable slab info.
>
> The current design uses "struct slabinfo" and get_slabinfo() to retrieve some
> info, i.e. active objs, etc. They are protected by CONFIG_SLABINFO.
Ok I guess then those need to be moved out of CONFIG_SLABINFO. Otherwise
dumping of slabs will not be supported when disabling that option.
Or dump CONFIG_SLABINFO ..
next prev parent reply other threads:[~2017-10-01 6:43 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
2017-09-27 21:59 ` Christopher Lameter
2017-09-27 22:11 ` Yang Shi
2017-10-01 6:43 ` Christopher Lameter [this message]
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=alpine.DEB.2.20.1710010142420.25658@nuc-kabylake \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--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 \
--cc=yang.s@alibaba-inc.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