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 v5] page_alloc: allow migration of smaller hugepages during contig_alloc
Date: Thu, 18 Dec 2025 16:32:07 -0500 [thread overview]
Message-ID: <aURy1x9D8fv_8CoW@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <01A47A14-3B5F-408B-AC37-64E36AFCF14C@nvidia.com>
On Thu, Dec 18, 2025 at 04:17:14PM -0500, Zi Yan wrote:
> On 18 Dec 2025, at 15:42, Gregory Price wrote:
>
> OK, you assume hugetlb is harder to migrate compared to other movable pages.
> Considering the limited number of hugetlb pages, it is quite possible.
> Anyway, I will wait for your v6. Thank you for the explanation and the
> prototype below.
>
They are harder - a migration starts with an allocation. Contiguous
allocations may then cause more migrations. We can end back up in similar
style search/migrate code.
Basically this can go some amount of recursive (though not much in practice).
We at least guarantee termination because we guarantee we won't attempt to
move pages of the same size or larger than the current allocation.
~Gregory
next prev parent reply other threads:[~2025-12-18 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 19:08 Gregory Price
2025-12-18 19:35 ` Johannes Weiner
2025-12-18 23:38 ` Gregory Price
2025-12-18 19:45 ` Zi Yan
2025-12-18 20:42 ` Gregory Price
2025-12-18 21:17 ` Zi Yan
2025-12-18 21:32 ` Gregory Price [this message]
2025-12-18 21:07 ` Gregory Price
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=aURy1x9D8fv_8CoW@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