[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <408d7eaa-5aea-4490-9fd0-978c4eb94d32@redhat.com>
Date: Tue, 19 Aug 2025 09:54:22 +0200
From: David Hildenbrand <david@...hat.com>
To: Mike Rapoport <rppt@...nel.org>, linux-mm@...ck.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Bill Wendling <morbo@...gle.com>, Daniel Jordan
<daniel.m.jordan@...cle.com>, Justin Stitt <justinstitt@...gle.com>,
Michael Ellerman <mpe@...erman.id.au>, Miguel Ojeda <ojeda@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH 3/4] mm/mm_init: drop deferred_init_maxorder()
>
> -static unsigned long __init
> -deferred_init_memmap_chunk(unsigned long start_pfn, unsigned long end_pfn,
> - struct zone *zone)
> -{
> - unsigned long nr_pages = 0;
> - unsigned long spfn, epfn;
> - u64 i = 0;
> + while (spfn < epfn) {
> + unsigned long mo_pfn = ALIGN(spfn + 1, MAX_ORDER_NR_PAGES);
> + unsigned long chunk_end = min(mo_pfn, epfn);
>
> - deferred_init_mem_pfn_range_in_zone(&i, zone, &spfn, &epfn, start_pfn);
> + nr_pages += deferred_init_pages(zone, spfn, chunk_end);
> + deferred_free_pages(spfn, chunk_end - spfn);
I assume the expectation is that all PFNs in the start_pfn -> end_pfn
range will go to this zone, correct?
--
Cheers
David / dhildenb
Powered by blists - more mailing lists