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: Tue, 12 May 2026 10:54:34 +0200 [thread overview]
Message-ID: <agLqyuQ8fyHBd0b1@tiehlicka> (raw)
In-Reply-To: <d5bd3927-3f80-4ed7-a8d2-0b7d58139286@easystack.cn>
On Tue 12-05-26 16:16:36, zhen.ni wrote:
> ## Implementation Plan
>
> 1. Add per-fd filtering to page_owner file
> - Add .open/.release/.write callbacks
> - Each file descriptor has its own filter state
> - Write filter commands: "nid=0", "mode=stack_handle"
>
> 2. Provide user-space tool
> - Simple CLI: ./page_owner_tool --nid=0
> - Handle fd management internally
>
> ## User Experience
>
> Direct access (default: no filter):
> cat /sys/kernel/debug/page_owner
>
> With filtering:
> ./page_owner_tool --nid=0
> ./page_owner_tool --nid=0,2-3
> ./page_owner_tool --nid=0 --mode=stack_handle
>
> ## Benefits
>
> - Completely eliminates race condition
> - Per-fd isolation for concurrent access
> - Correct design for multi-consumer scenarios
>
> Does this approach look good to you?
>
> Please let me know if you have any suggestions or concerns.
Yes, this is what I had in mind.
Thanks for looking into that.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2026-05-12 8:54 UTC|newest]
Thread overview: 16+ 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 ` [PATCH v6 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering Michal Hocko
2026-05-11 12:40 ` zhen.ni
2026-05-11 12:54 ` Michal Hocko
2026-05-12 3:11 ` zhen.ni
2026-05-12 7:26 ` Michal Hocko
2026-05-12 8:16 ` zhen.ni
2026-05-12 8:54 ` Michal Hocko [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=agLqyuQ8fyHBd0b1@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