From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Muchun Song <muchun.song@linux.dev>,
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 15:53:56 -0700 [thread overview]
Message-ID: <20260727155356.2b2d39657d1154f9400e69ea@linux-foundation.org> (raw)
In-Reply-To: <amcuEiLzIunJwZVx@kernel.org>
On Mon, 27 Jul 2026 13:08:18 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> 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? ;-)
Well it's supposed to be. Rebases are rare.
The larger problem is that it doesn't contain anything until -rc5ish
because we haven't stabilized anything yet!
> > 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.
No probs, I'll drop it when Mark reports the duplicate.
prev parent reply other threads:[~2026-07-27 22:54 UTC|newest]
Thread overview: 12+ 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 02/21] kho: make radix max key width more obvious 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 12/21] kho: add kho_radix_init_tree() 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 17/21] mm/mm_init: don't rely on memblock to get KHO scratch migratetype Pratyush Yadav
2026-07-25 17:21 ` [PATCH v4 19/21] memblock: make HugeTLB bootmem allocation work with KHO Pratyush Yadav
[not found] ` <20260725172133.4018491-17-pratyush@kernel.org>
2026-07-26 10:16 ` [PATCH v4 16/21] mm/mm_init: simplify deferred_free_pages() migratetype init Mike Rapoport
2026-07-27 3:25 ` Andrew Morton
2026-07-27 3:43 ` Muchun Song
2026-07-27 10:08 ` Mike Rapoport
2026-07-27 22:53 ` Andrew Morton [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=20260727155356.2b2d39657d1154f9400e69ea@linux-foundation.org \
--to=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=rppt@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;
as well as URLs for NNTP newsgroup(s).