From: Mike Rapoport <rppt@kernel.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pratyush Yadav <pratyush@kernel.org>,
David Hildenbrand <david@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Alexander Graf <graf@amazon.com>,
Oscar Salvador <osalvador@suse.de>,
Jason Miu <jasonmiu@google.com>,
Jork Loeser <jloeser@linux.microsoft.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH v4 16/21] mm/mm_init: simplify deferred_free_pages() migratetype init
Date: Mon, 27 Jul 2026 13:08:18 +0300 [thread overview]
Message-ID: <amcuEiLzIunJwZVx@kernel.org> (raw)
In-Reply-To: <92E24479-07A8-4998-9607-87420A8BE04E@linux.dev>
On Mon, Jul 27, 2026 at 11:43:31AM +0800, Muchun Song wrote:
>
>
> > On Jul 27, 2026, at 11:25, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Sun, 26 Jul 2026 13:16:54 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> >
> >> On Sat, Jul 25, 2026 at 07:21:16PM +0200, Pratyush Yadav wrote:
> >>> From: Muchun Song <songmuchun@bytedance.com>
> >>>
> >>> deferred_free_pages() open-codes two loops to initialize the pageblock
> >>> migratetype for a range of pages.
> >>>
> >>> Replace them with pageblock_migratetype_init_range() to remove the
> >>> duplication and make the code clearer (Note that deferred_free_pages() may
> >>> be called from atomic context).
> >>>
> >>> Link: https://lore.kernel.org/20260612035903.2468601-6-songmuchun@bytedance.com
> >>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> >>> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> >>> Acked-by: Oscar Salvador <osalvador@suse.de>
> >>> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> >>> ---
> >>>
> >>> Notes:
> >>> This patch is taken from Muchun's series [0]. The patch as of today is
> >>> in mm-unstable.
> >>
> >> @Andrew,
> >>
> >> It looks like it'll take some time for this patch to get into mm-stable so
> >> we can't base this work on a branch in the mm tree :(
> >
> > I didn't know anyone was using mm-stable :(
Maybe nobody uses it because it's not really stable? ;-)
> > Series is adequately reviewed and is near head-of-queue so I can move
> > it into mm-stable a few days hence if that helps?
> >
> >> I'd like to expose the KHO scratch extension to linux-next ASAP so I'm
> >> inclined to take this patch as a part of this series and live for a while
> >> with a duplicated commit in linux-next. Once this patch would be in
> >> mm-stable we can rebase kho-scratch work on top of mm-stable and hopefully
> >> there will be enough time for it to live in linux-next so that Linus won't
> >> get angry at us :)
> >>
> >> How does that sound to you?
> >
> > That's fine - let me know what you choose to do and I'll adapt to it.
> >
> > An unknown (to me) is whether Muchun's series "mm: Refactor bootmem
> > gigantic hugepage allocation, v4" still works with this patch removed. Everything
> > applies OK for what that's worth.
>
> Hi Andrew,
>
> I'd like to confirm that this is a completely independent cleanup patch,
> so it can be merged on its own.
That's great, thanks for confirming!
Then I think the easiest would be to take "mm/mm_init: simplify
deferred_free_pages() migratetype init" via liveupdate tree.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-07-27 10:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 17:21 [PATCH v4 00/21] kho: make boot time huge page allocation work nicely with KHO Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 01/21] kho: generalize radix tree APIs Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 02/21] kho: make radix max key width more obvious Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 03/21] kho: disallow wide keys in radix tree Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 04/21] kho: return virtual address of mem_map from kho_get_mem_map() Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 05/21] kho: store incoming radix tree in kho_in Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 06/21] kho: move all memory retrieval logic to kho_mem_retrieve() Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 07/21] kho: add a struct for radix callbacks Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 08/21] kho: add callback for table pages Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 09/21] kho: add data argument to radix walk callback Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 10/21] kho: allow early-boot usage of the KHO radix tree Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 11/21] kho: allow destroying " Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 12/21] kho: add kho_radix_init_tree() Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 13/21] kho: expose kho_scratch_overlap() to kexec_handover.h Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 14/21] kho: initialize kho_scratch pointer earlier in boot Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 15/21] kho: initialize preserved memory map radix tree earlier Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 16/21] mm/mm_init: simplify deferred_free_pages() migratetype init Pratyush Yadav
2026-07-26 10:16 ` Mike Rapoport
2026-07-27 3:25 ` Andrew Morton
2026-07-27 3:43 ` Muchun Song
2026-07-27 10:08 ` Mike Rapoport [this message]
2026-07-25 17:21 ` [PATCH v4 17/21] mm/mm_init: don't rely on memblock to get KHO scratch migratetype Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 18/21] kho: extend scratch Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 19/21] memblock: make HugeTLB bootmem allocation work with KHO Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 20/21] memblock: add memblock_reserved_hugetlb_size() Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 21/21] kho: exclude hugetlb memory from scratch size calculation Pratyush Yadav
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=amcuEiLzIunJwZVx@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=jloeser@linux.microsoft.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=songmuchun@bytedance.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