From: Gregory Price <gourry@gourry.net>
To: Zi Yan <ziy@nvidia.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, akpm@linux-foundation.org, vbabka@suse.cz,
surenb@google.com, mhocko@suse.com, jackmanb@google.com,
hannes@cmpxchg.org, richard.weiyang@gmail.com, osalvador@suse.de,
rientjes@google.com, david@redhat.com, joshua.hahnjy@gmail.com,
fvdl@google.com
Subject: Re: [PATCH v6] page_alloc: allow migration of smaller hugepages during contig_alloc
Date: Fri, 19 Dec 2025 15:59:02 -0500 [thread overview]
Message-ID: <aUW8lsodni9C583j@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <1E3BF4A4-C8F5-4FB9-A658-9D40804CDAD6@nvidia.com>
On Fri, Dec 19, 2025 at 03:48:45PM -0500, Zi Yan wrote:
> On 18 Dec 2025, at 18:38, Gregory Price wrote:
>
> > + if (PageHuge(page)) {
> > + unsigned int order;
> > +
> > + if (!IS_ENABLED(CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION))
> > + return false;
> > +
> > + if (skip_hugetlb) {
> > + *skipped_hugetlb = true;
>
> I do not know whether we should check if skipped_hugetlb is NULL or not,
> since pfn_range_valid_contig() is only called by alloc_contig_pages_noprof().
> I have no strong opinion on an additional skipped_hugetlb check.
>
I'm fine either way if folks have a preference. Compiler might even
optimize it anyway after things get inlined.
> Otherwise, LGTM.
>
> Reviewed-by: Zi Yan <ziy@nvidia.com>
>
Thanks again!
~Gregory
prev parent reply other threads:[~2025-12-19 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 23:38 Gregory Price
2025-12-19 0:08 ` Wei Yang
2025-12-19 14:26 ` Gregory Price
2025-12-19 20:46 ` Zi Yan
2025-12-19 20:56 ` Gregory Price
2025-12-20 6:37 ` Wei Yang
2025-12-21 11:32 ` Gregory Price
2025-12-21 12:42 ` Gregory Price
2025-12-19 20:48 ` Zi Yan
2025-12-19 20:59 ` Gregory Price [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=aUW8lsodni9C583j@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fvdl@google.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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