From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Ye Liu <ye.liu@linux.dev>, Andrew Morton <akpm@linux-foundation.org>
Cc: Ye Liu <liuye@kylinos.cn>, David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] tools/mm/page_owner_sort: fix --sort, add module filter, improve usage
Date: Thu, 23 Jul 2026 10:59:08 +0200 [thread overview]
Message-ID: <d5eed495-1544-4783-813d-e879004603cb@kernel.org> (raw)
In-Reply-To: <20260722023726.600200-1-ye.liu@linux.dev>
On 7/22/26 04:37, Ye Liu wrote:
> From: Ye Liu <liuye@kylinos.cn>
>
> This series improves the page_owner_sort tool with a bug fix, a new
> module-name feature, and better usage text.
For some reason, patches 1 and 3 have very limited recipient list compared
to 0 and 2, please fix when sending a v2.
> Patch 1 fixes a long-standing bug where --sort was silently ignored
> when used without a short option (-a, -m, -p, etc.). The COMP_NO_FLAG
> case fell through to COMP_NUM and overwrote the sort conditions
> configured by parse_sort_args().
>
> Patch 2 adds kernel module name support for sort, cull, and filter
> operations. Page owner stack traces already contain module names in
> the [module] format produced by %pS, but page_owner_sort had no way
> to use them. Records without module frames are assigned "vmlinux".
>
> # Aggregate page usage per module
> ./page_owner_sort input.txt output.txt --cull=mod
>
> # Filter to records from xfs module only
> ./page_owner_sort input.txt output.txt --module xfs
>
> # Sort by module name, then by pid descending
> ./page_owner_sort input.txt output.txt --sort=mod,-pid
>
> Patch 3 lists all available sort keys with abbreviations and examples
> directly in the --sort help section so users no longer need to read
> the source to discover valid keys.
>
> Ye Liu (3):
> tools/mm/page_owner_sort: fix --sort option being silently ignored
> tools/mm/page_owner_sort: add module name sort/cull/filter support
> tools/mm/page_owner_sort: show available sort keys in usage text
>
> Documentation/mm/page_owner.rst | 8 +-
> tools/mm/page_owner_sort.c | 125 +++++++++++++++++++++++++++-----
> 2 files changed, 113 insertions(+), 20 deletions(-)
>
prev parent reply other threads:[~2026-07-23 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 2:37 [PATCH 0/3] tools/mm/page_owner_sort: fix --sort, add module filter, improve usage Ye Liu
2026-07-22 2:37 ` [PATCH 2/3] tools/mm/page_owner_sort: add module name sort/cull/filter support Ye Liu
2026-07-23 0:01 ` [PATCH 0/3] tools/mm/page_owner_sort: fix --sort, add module filter, improve usage Andrew Morton
2026-07-23 8:59 ` Vlastimil Babka (SUSE) [this message]
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=d5eed495-1544-4783-813d-e879004603cb@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox