From: "Harry Yoo (Oracle)" <harry@kernel.org>
To: Hao Li <hao.li@linux.dev>
Cc: vbabka@kernel.org, akpm@linux-foundation.org, cl@gentwo.org,
rientjes@google.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slub: use N_NORMAL_MEMORY in can_free_to_pcs to handle remote frees
Date: Fri, 3 Apr 2026 21:02:22 +0900 [thread overview]
Message-ID: <ac-qJ7tYQ-ybegOw@hyeyoo> (raw)
In-Reply-To: <20260403073958.8722-1-hao.li@linux.dev>
On Fri, Apr 03, 2026 at 03:37:36PM +0800, Hao Li wrote:
> Memory hotplug now keeps N_NORMAL_MEMORY up to date correctly, so make
> can_free_to_pcs() use it.
>
> As a result, when freeing objects on memoryless nodes, or on nodes that
> have memory but only in ZONE_MOVABLE, the objects can be freed to the
> sheaf instead of going through the slow path.
>
> Signed-off-by: Hao Li <hao.li@linux.dev>
> ---
Acked-by: Harry Yoo (Oracle) <harry@kernel.org>
> Hi Vlastimil, this patch depends on a prerequisite patch[1] from a few days
> ago. I'm not sure how this should be handled.
> I wonder if Andrew might put them in the same tree.
But it also depends on the patch series
"[PATCH 0/3] slab: support memoryless nodes with sheaves".
So perhaps better send it to Linus after 7.1-rc1?
Thanks!
> [1] https://lore.kernel.org/linux-mm/20260330035941.518186-1-hao.li@linux.dev/
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-04-03 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 7:37 [PATCH] slub: use N_NORMAL_MEMORY in can_free_to_pcs to handle remote frees Hao Li
2026-04-03 12:02 ` Harry Yoo (Oracle) [this message]
2026-04-03 18:14 ` Vlastimil Babka (SUSE)
2026-04-04 4:05 ` Hao Li
2026-04-06 1:57 ` Harry Yoo (Oracle)
2026-04-03 18:02 ` David Rientjes
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=ac-qJ7tYQ-ybegOw@hyeyoo \
--to=harry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@kernel.org \
/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