From: Alistair Popple <apopple@nvidia.com>
To: Li Zhe <lizhe.67@bytedance.com>
Cc: rppt@kernel.org, akpm@linux-foundation.org, arnd@arndb.de,
bp@alien8.de, dave.hansen@linux.intel.com, david@kernel.org,
kees@kernel.org, linux-arch@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@redhat.com, tglx@kernel.org,
x86@kernel.org
Subject: Re: [PATCH v5 4/8] mm: add a template-based fast path for zone-device page init
Date: Tue, 7 Jul 2026 13:06:02 +1000 [thread overview]
Message-ID: <akxsbwyfYH1LCyGm@nvdebian.thelocal> (raw)
In-Reply-To: <20260706074527.23978-1-lizhe.67@bytedance.com>
On 2026-07-06 at 17:45 +1000, Li Zhe <lizhe.67@bytedance.com> wrote...
> On Fri, 3 Jul 2026 17:06:33 +0300, rppt@kernel.org wrote:
>
> > On Wed, Jul 01, 2026 at 05:05:49PM +0800, Li Zhe wrote:
> > > memmap_init_zone_device() repeats nearly identical head-page
> > > initialization for each PFN. Prepare one reusable ZONE_DEVICE head-page
> > > template through the existing slow path, refresh the PFN-dependent
> > > fields in that template before each copy, and memcpy it into each
> > > destination page.
> > >
> > > This reduces the average rebind time from 244.28 ms to 217.19 ms, or
> > > about 11%.
> > >
> > > Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
> > > ---
> > > mm/mm_init.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++--
> > > 1 file changed, 74 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/mm/mm_init.c b/mm/mm_init.c
> > > index 4c7fad440c2a..cc8417951467 100644
> > > --- a/mm/mm_init.c
> > > +++ b/mm/mm_init.c
> > > @@ -1066,6 +1066,50 @@ static void __ref zone_device_page_init_slow(struct page *page,
> > > set_page_count(page, 0);
> > > }
> > >
> > > +static inline bool zone_device_page_init_optimization_enabled(void)
> > > +{
> > > + /*
> > > + * The template fast path copies a preinitialized struct page image.
> > > + * Skip it when the page_ref_set tracepoint is enabled.
> > > + */
> > > + return !page_ref_tracepoint_active(page_ref_set);
> > > +}
> > > +
> > > +static inline void zone_device_template_page_init(struct page *template,
> > > + struct page *src)
> > > +{
> > > + memcpy(template, src, sizeof(*template));
> > > +}
> > > +
> > > +/*
> > > + * 'template' is a reusable page prototype rather than a strictly immutable
> > > + * object. Most ZONE_DEVICE fields stay constant across the pages covered by
> > > + * the current template, but section bits and page->virtual may still depend
> > > + * on the PFN. Refresh those PFN-dependent fields in the template before
> > > + * copying it into @page.
> > > + */
> > > +static inline void zone_device_page_update_template(struct page *template,
> > > + unsigned long pfn)
> > > +{
> > > + set_page_section_from_pfn(template, pfn);
> > > +#ifdef WANT_PAGE_VIRTUAL
> > > + if (!is_highmem_idx(ZONE_DEVICE))
> > > + set_page_address(template, __va(pfn << PAGE_SHIFT));
> > > +#endif
> > > +}
> > > +
> > > +static void zone_device_page_init_from_template(struct page *page,
> > > + unsigned long pfn, struct page *template)
> > > +{
> > > + /*
> > > + * 'template' carries the invariant portion of a ZONE_DEVICE struct
> > > + * page. Update the PFN-dependent fields in place before copying it
> > > + * to the destination page.
> > > + */
> > > + zone_device_page_update_template(template, pfn);
> > > + memcpy(page, template, sizeof(*page));
> > > +}
> > > +
> >
> > The whole bunch of template functions look like it could be useful for
> > initialization of the non-zone-device struct pages as well.
> >
> > As I mentioned previously, it's interesting to see if this approach speeds
> > up normal memory map initialization as well. If if does could have a single
> > set of the template functions.
>
> Thanks for the suggestion. I agree this is worth exploring.
>
> For this series, I would prefer to keep the scope limited to the
> ZONE_DEVICE initialization path and get that part settled first.
I think that makes sense, especially as my initial perf testing with other types
of ZONE_DEVICE pages without altmap didn't show much of a perf impact. Meaning
it might not be so useful for normal page init.
> After this series is settled, I plan to look into whether a similar
> template-based approach can also help normal page initialization. If it
> shows a real benefit there as well, I can follow up with a separate
> series.
I agree it would be interesting though, please let us know what you find one way
or the other.
- Alistair
> Thanks,
> Zhe
next prev parent reply other threads:[~2026-07-07 3:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 9:05 [PATCH v5 0/8] mm: optimize zone-device memmap initialization Li Zhe
2026-07-01 9:05 ` [PATCH v5 1/8] mm: fix stale ZONE_DEVICE refcount comment Li Zhe
2026-07-06 9:11 ` David Hildenbrand (Arm)
2026-07-07 2:28 ` Alistair Popple
2026-07-01 9:05 ` [PATCH v5 2/8] mm: factor zone-device page init helpers out of __init_zone_device_page Li Zhe
2026-07-06 9:13 ` David Hildenbrand (Arm)
2026-07-06 11:50 ` Li Zhe
2026-07-06 13:47 ` David Hildenbrand (Arm)
2026-07-07 3:25 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 3/8] mm: add a set_page_section_from_pfn() helper Li Zhe
2026-07-06 9:15 ` David Hildenbrand (Arm)
2026-07-06 11:52 ` Li Zhe
2026-07-06 13:48 ` David Hildenbrand (Arm)
2026-07-07 3:26 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 4/8] mm: add a template-based fast path for zone-device page init Li Zhe
2026-07-03 14:06 ` Mike Rapoport
2026-07-06 7:45 ` Li Zhe
2026-07-07 3:06 ` Alistair Popple [this message]
2026-07-07 6:36 ` Li Zhe
2026-07-07 3:02 ` Alistair Popple
2026-07-07 6:33 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 5/8] mm: extend the template fast path to zone-device compound tails Li Zhe
2026-07-07 3:09 ` Alistair Popple
2026-07-07 6:38 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 6/8] string: introduce memcpy_nt() helpers Li Zhe
2026-07-06 9:18 ` David Hildenbrand (Arm)
2026-07-06 11:53 ` Li Zhe
2026-07-06 13:49 ` David Hildenbrand (Arm)
2026-07-07 3:28 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 7/8] x86/string: extend memcpy_flushcache() fixed-size fastpaths Li Zhe
2026-07-01 9:05 ` [PATCH v5 8/8] mm: use memcpy_nt() in zone-device template copies Li Zhe
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=akxsbwyfYH1LCyGm@nvdebian.thelocal \
--to=apopple@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhe.67@bytedance.com \
--cc=mingo@redhat.com \
--cc=rppt@kernel.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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