From: Michal Hocko <mhocko@suse.com>
To: Zhen Ni <zhen.ni@easystack.cn>
Cc: akpm@linux-foundation.org, vbabka@kernel.org, surenb@google.com,
jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering
Date: Mon, 11 May 2026 14:23:52 +0200 [thread overview]
Message-ID: <agHKWCw3CFO0CZ_E@tiehlicka> (raw)
In-Reply-To: <20260511033017.747781-1-zhen.ni@easystack.cn>
On Mon 11-05-26 11:30:14, Zhen Ni wrote:
> Solution
> ========
>
> This patch series introduces a flexible filter infrastructure with
> two initial filters:
>
> 1. **Print Mode Filter**: Outputs only stack handles instead of
> full stack traces. The handle-to-stack mapping can be retrieved
> from the existing show_stacks_handles interface. This dramatically
> reduces output size while preserving all allocation metadata.
>
> 2. **NUMA Node Filter**: Allows filtering pages by specific NUMA node(s)
> using flexible nodelist format, enabling targeted analysis of memory
> issues in NUMA-aware deployments.
How does this work when there are multiple consumers of the interface?
E.g per numa tool to watch node lock page_owner information?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2026-05-11 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 3:30 [PATCH v6 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering Zhen Ni
2026-05-11 3:30 ` [PATCH v6 1/3] mm/page_owner: add print_mode filter Zhen Ni
2026-05-11 8:29 ` Oscar Salvador
2026-05-11 11:54 ` zhen.ni
2026-05-11 3:30 ` [PATCH v6 2/3] mm/page_owner: add NUMA node filter with nodelist support Zhen Ni
2026-05-11 8:54 ` Oscar Salvador
2026-05-11 12:24 ` zhen.ni
2026-05-11 3:30 ` [PATCH v6 3/3] mm/page_owner: document page_owner filter features Zhen Ni
2026-05-11 8:33 ` Oscar Salvador
2026-05-11 12:23 ` Michal Hocko [this message]
2026-05-11 12:40 ` [PATCH v6 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering zhen.ni
2026-05-11 12:54 ` 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=agHKWCw3CFO0CZ_E@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=zhen.ni@easystack.cn \
--cc=ziy@nvidia.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