From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm, oom: disable dump_tasks by default
Date: Wed, 4 Sep 2019 07:40:04 +0200 [thread overview]
Message-ID: <20190904054004.GA3838@dhcp22.suse.cz> (raw)
In-Reply-To: <af0703d2-17e4-1b8e-eb54-58d7743cad60@i-love.sakura.ne.jp>
On Wed 04-09-19 05:52:43, Tetsuo Handa wrote:
> On 2019/09/03 23:45, Michal Hocko wrote:
> > It's primary purpose is
> > to help analyse oom victim selection decision.
>
> I disagree, for I use the process list for understanding what / how many
> processes are consuming what kind of memory (without crashing the system)
> for anomaly detection purpose. Although we can't dump memory consumed by
> e.g. file descriptors, disabling dump_tasks() loose that clue, and is
> problematic for me.
Does anything really prevent you from enabling this by sysctl though? Or
do you claim that this is a general usage pattern and therefore the
default change is not acceptable or do you want a changelog to be
updated?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-09-04 5:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 14:45 Michal Hocko
2019-09-03 15:02 ` Qian Cai
2019-09-03 15:13 ` Michal Hocko
2019-09-03 15:32 ` Qian Cai
2019-09-03 19:12 ` Michal Hocko
2019-09-05 16:10 ` Qian Cai
[not found] ` <8ea5da51-a1ac-4450-17d9-0ea7be346765@i-love.sakura.ne.jp>
2019-09-05 21:21 ` Qian Cai
[not found] ` <192f2cb9-172e-06f4-d9e4-a58b5e167231@i-love.sakura.ne.jp>
2019-09-06 13:08 ` Qian Cai
[not found] ` <7eada349-90d0-a12f-701c-adac3c395e3c@i-love.sakura.ne.jp>
2019-09-06 13:48 ` Qian Cai
2019-09-06 13:49 ` Michal Hocko
[not found] ` <af0703d2-17e4-1b8e-eb54-58d7743cad60@i-love.sakura.ne.jp>
2019-09-04 5:40 ` Michal Hocko [this message]
2019-09-04 20:04 ` David Rientjes
[not found] ` <12bcade2-4190-5e5e-35c6-7a04485d74b9@i-love.sakura.ne.jp>
2019-09-05 14:08 ` Michal Hocko
[not found] ` <20ec856d-0f1e-8903-dbe0-bbc8b7a1847a@i-love.sakura.ne.jp>
2019-09-06 11:02 ` Michal Hocko
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=20190904054004.GA3838@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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