From: Michal Hocko <mhocko@suse.com>
To: Ye Liu <ye.liu@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ye Liu <liuye@kylinos.cn>, David Rientjes <rientjes@google.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm/oom_kill: dump top 5 memory consumers by RSS in OOM report
Date: Thu, 13 Aug 2026 10:12:21 +0200 [thread overview]
Message-ID: <an18ZbYWit7oiwHl@tiehlicka> (raw)
In-Reply-To: <20260811062924.4123014-1-ye.liu@linux.dev>
On Tue 11-08-26 14:29:24, Ye Liu wrote:
> From: Ye Liu <liuye@kylinos.cn>
>
> When the OOM killer triggers, dump_tasks() prints every task's memory
> state but in no particular order. On systems with hundreds of
> processes, identifying the heaviest memory consumers requires manual
> log post-processing.
Yes, but why is that a problem? It should be a pretty easy script, no?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2026-08-13 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 6:29 [RFC PATCH] mm/oom_kill: dump top 5 memory consumers by RSS in OOM report Ye Liu
2026-08-13 8:12 ` Michal Hocko [this message]
2026-08-13 9:48 ` Ye Liu
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=an18ZbYWit7oiwHl@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=rientjes@google.com \
--cc=shakeel.butt@linux.dev \
--cc=ye.liu@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.