From: "zhen.ni" <zhen.ni@easystack.cn>
To: SeongJae Park <sj@kernel.org>
Cc: akpm@linux-foundation.org, vbabka@kernel.org, surenb@google.com,
mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] mm/page_owner: add NUMA node filter with nodelist support
Date: Sat, 9 May 2026 15:27:22 +0800 [thread overview]
Message-ID: <9ebddab1-b7b4-462e-a920-f850cc5c55c5@easystack.cn> (raw)
In-Reply-To: <20260509004417.84229-1-sj@kernel.org>
在 2026/5/9 08:44, SeongJae Park 写道:
> On Thu, 7 May 2026 14:46:42 +0800 Zhen Ni <zhen.ni@easystack.cn> wrote:
>
>> Add NUMA node filtering functionality to page_owner to allow filtering
>> pages by specific NUMA node(s). This is useful for NUMA-aware memory
>> allocation analysis and debugging.
>>
>> The filter supports flexible nodelist input formats:
>> - Single node: echo "0" > nid
>> - Multiple nodes: echo "0,2,3" > nid
>> - Node range: echo "0-3" > nid
>> - Mixed format: echo "0,2-4,7" > nid
>> - Clear filter: echo > nid (empty string)
>>
>> The implementation uses nodemask_t for efficient multi-node filtering
>> and nodelist_parse() for flexible input parsing. Empty input clears
>> the filter.
>>
>> Note: Access to nid_mask uses plain load/store without locking because
>> nodemask_t is too large (128 bytes) for READ_ONCE/WRITE_ONCE. This is
>> safe for debug use: low-frequency changes and torn reads would only
>> cause temporary inconsistency in debug output.
>>
>> Signed-off-by: Zhen Ni <zhen.ni@easystack.cn>
>> ---
>>
>> Changes in v5:
>> - Optimize nodes_empty() check in page iteration loop
>> - Add __data_racy qualifier to nid_mask field
>
> Adding links to previous revisions [1] would be helpful.
Will add lore links.
>
>> ---
>> mm/page_owner.c | 86 +++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 86 insertions(+)
>>
>> diff --git a/mm/page_owner.c b/mm/page_owner.c
> [...]
>> @@ -700,6 +707,9 @@ read_page_owner(struct file *file, char __user *buf, size_t count, loff_t *ppos)
>> while (!pfn_valid(pfn) && (pfn & (MAX_ORDER_NR_PAGES - 1)) != 0)
>> pfn++;
>>
>> + mask = owner_filter.nid_mask;
>> + bool filter_by_nid = !nodes_empty(mask);
>> +
>
> Shouldn't we separate variable declarations and statements inside a same block?
>
I will fix this in v6 by declaring all variables at the beginning of the
block:
nodemask_t mask;
bool filter_by_nid;
mask = owner_filter.nid_mask;
filter_by_nid = !nodes_empty(mask);
> [...]
>> +static ssize_t nid_filter_write(struct file *file,
>> + const char __user *buf,
>> + size_t count, loff_t *ppos)
>> +{
>> + char *kbuf;
>> + nodemask_t mask;
>> + int ret;
>> +
>> + /*
>> + * Limit input size to handle worst-case nodelist (all nodes).
>> + * Worst case per node: ",NNNNN" (comma + 5-digit node number) = 6 bytes.
>> + * Formula: 100 bytes overhead + 6 * MAX_NUMNODES
>
> What is the 100 bytes overhead?
The 100 bytes is intended as a safety margin, but it's not strictly
necessary.
Maybe I should simplify it to just 6 * MAX_NUMNODES?
>
>> + */
>> + if (count > (100 + 6 * MAX_NUMNODES))
>> + return -EINVAL;
>> +
>> + kbuf = kmalloc(count + 1, GFP_KERNEL);
>> + if (!kbuf)
>> + return -ENOMEM;
>
> Would it make sense to use kmalloc_objs()?
I'll update the code to use
kmalloc_objs(char, count + 1, GFP_KERNEL)
Thanks for the review!
>
> [1] https://docs.kernel.org/process/submitting-patches.html#commentary
>
>
> Thanks,
> SJ
>
> [...]
>
>
Best regards,
Zhen
next prev parent reply other threads:[~2026-05-09 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 6:46 [PATCH v5 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering Zhen Ni
2026-05-07 6:46 ` [PATCH v5 1/3] mm/page_owner: add print_mode filter Zhen Ni
2026-05-08 21:13 ` Andrew Morton
2026-05-09 0:29 ` SeongJae Park
2026-05-09 6:54 ` zhen.ni
2026-05-07 6:46 ` [PATCH v5 2/3] mm/page_owner: add NUMA node filter with nodelist support Zhen Ni
2026-05-09 0:44 ` SeongJae Park
2026-05-09 7:27 ` zhen.ni [this message]
2026-05-09 15:35 ` SeongJae Park
2026-05-07 6:46 ` [PATCH v5 3/3] mm/page_owner: document page_owner filter features Zhen Ni
2026-05-09 0:51 ` SeongJae Park
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=9ebddab1-b7b4-462e-a920-f850cc5c55c5@easystack.cn \
--to=zhen.ni@easystack.cn \
--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=mhocko@suse.com \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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