From: Andrew Morton <akpm@linux-foundation.org>
To: Frank van der Linden <fvdl@google.com>
Cc: muchun.song@linux.dev, linux-mm@kvack.org, yuzhao@google.com,
usamaarif642@gmail.com, joao.m.martins@oracle.com,
roman.gushchin@linux.dev, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH mm-unstable] mm: make SPARSEMEM_VMEMMAP_PREINIT an internal option
Date: Thu, 27 Feb 2025 16:12:31 -0800 [thread overview]
Message-ID: <20250227161231.3b998da64aa029917d1fc9b8@linux-foundation.org> (raw)
In-Reply-To: <20250227185717.1265644-1-fvdl@google.com>
On Thu, 27 Feb 2025 18:57:17 +0000 Frank van der Linden <fvdl@google.com> wrote:
> SPARSEMEM_VMEMMAP_PREINIT is not useful as a user-facing
> option, it is just something that should be selected
> if a subsystem wishes to do vmemmap preinit. That's
> currently only HUGETLB_PAGE_OPTIMIZE_VMEMMAP.
>
> So, make it a default-less option that is only selected
> by HUGETLB_PAGE_OPTIMIZE_VMEMMAP, iff the architecture
> has noted it is capable of doing hugetlb vmemmap preinit.
> That is done via ARCH_WANT_HUGETLB_VMEMMAP_PREINIT,
> renamed from ARCH_WANT_SPARSE_VMEMMAP_PREINIT.
>
I'm in a mess getting this landed in the right place in the series. We
seem to have a few updates in the works so I'll drop this series again.
And I'll disable Mike's "mm/mm_init: rename __init_reserved_page_zone
to __init_page_from_nid" and "mm/mm_init: rename init_reserved_page to
init_deferred_page" until "hugetlb/CMA improvements for large systems
v5" appears.
next prev parent reply other threads:[~2025-02-28 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 18:57 Frank van der Linden
2025-02-27 19:07 ` Frank van der Linden
2025-02-27 19:12 ` Frank van der Linden
2025-02-27 19:52 ` Johannes Weiner
2025-02-28 0:12 ` Andrew Morton [this message]
2025-02-28 16:44 ` Frank van der Linden
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=20250227161231.3b998da64aa029917d1fc9b8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fvdl@google.com \
--cc=hannes@cmpxchg.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=usamaarif642@gmail.com \
--cc=yuzhao@google.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