From: Gregory Price <gourry@gourry.net>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
kernel-team@meta.com, vbabka@suse.cz, surenb@google.com,
mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
ziy@nvidia.com, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@suse.de>,
Alexandru Moise <00moses.alexander00@gmail.com>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH v2] mm, hugetlb: implement movable_gigantic_pages sysctl
Date: Tue, 25 Nov 2025 08:15:37 -0500 [thread overview]
Message-ID: <aSWr-frCzG8_z3S3@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <c309a251-5d14-49a9-a3d7-5c60d100c4eb@kernel.org>
On Tue, Nov 25, 2025 at 11:24:24AM +0100, David Hildenbrand (Red Hat) wrote:
> On 11/21/25 20:27, Gregory Price wrote:
>
> Can we also reference this parameter here from
> Documentation/admin-guide/mm/memory-hotplug.rst?
>
Good call
> In particular, there we also talk about gigantic pages and the interaction
> with ZONE_MOVABLE:
>
> "
> - Gigantic pages are unmovable, resulting in user space consuming a
> lot of unmovable memory.
>
> - Huge pages are unmovable when an architectures does not support huge
> page migration, resulting in a similar issue as with gigantic pages.
> "
>
> And then later, we talk about "Even with ZONE_MOVABLE, there are some corner
> cases where offlining a memory
> block might fail:" where this should be spelled out as well.
>
I will take a look, thank you!
> --
> Cheers
>
> David
prev parent reply other threads:[~2025-11-25 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 19:27 Gregory Price
2025-11-25 10:24 ` David Hildenbrand (Red Hat)
2025-11-25 13:15 ` 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=aSWr-frCzG8_z3S3@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=00moses.alexander00@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.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