Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: "zhen.ni" <zhen.ni@easystack.cn>
Cc: SeongJae Park <sj@kernel.org>,
	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 08:35:45 -0700	[thread overview]
Message-ID: <20260509153547.89036-1-sj@kernel.org> (raw)
In-Reply-To: <9ebddab1-b7b4-462e-a920-f850cc5c55c5@easystack.cn>

On Sat, 9 May 2026 15:27:22 +0800 "zhen.ni" <zhen.ni@easystack.cn> wrote:

> 
> 
> 在 2026/5/9 08:44, SeongJae Park 写道:
> > On Thu,  7 May 2026 14:46:42 +0800 Zhen Ni <zhen.ni@easystack.cn> wrote:
[...]
> >> +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?

I wouldn't mind keep having 100 bytes, but I'd suggest to clearly document the
intention if you will do so.  But if you also don't think it is necessary, I'm
also up to just removing it.

> > 
> >> +	 */
> >> +	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)

kmalloc_objs() use GFP_KERNEL by default.  It can also understand the type of
the ojbect.  So you could kmalloc_objs(*kbuf, count + 1).

> 
> Thanks for the review!

I'm happy to help! :)


Thanks,
SJ

[...]


  reply	other threads:[~2026-05-09 15:35 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
2026-05-09 15:35       ` SeongJae Park [this message]
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=20260509153547.89036-1-sj@kernel.org \
    --to=sj@kernel.org \
    --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=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