From: Mike Rapoport <rppt@kernel.org>
To: Li Zhe <lizhe.67@bytedance.com>
Cc: akpm@linux-foundation.org, apopple@nvidia.com, arnd@arndb.de,
balbirs@nvidia.com, bp@alien8.de, dave.hansen@linux.intel.com,
david@kernel.org, kees@kernel.org, mingo@redhat.com,
muchun.song@linux.dev, tglx@kernel.org,
linux-arch@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: Re: [PATCH v11 3/7] mm: add a template-based fast path for zone-device page init
Date: Wed, 2 Sep 2026 07:16:12 +0300 [thread overview]
Message-ID: <apejDEdW95T-tekb@kernel.org> (raw)
In-Reply-To: <20260831111638.76012-4-lizhe.67@bytedance.com>
On Mon, Aug 31, 2026 at 07:16:34PM +0800, Li Zhe wrote:
> memmap_init_zone_device() repeats nearly identical head-page
> initialization for each PFN. Initialize the first real ZONE_DEVICE head
> page through the existing path, copy that final state into a reusable
> template, refresh the PFN-dependent fields in that template before each
> copy, and copy it into the remaining destination pages.
>
> Use the template path unconditionally. The page_ref_set tracepoint is
> primarily a debugging aid, while this code is still initializing struct
> pages before they are handed out. From the perspective of users of those
> pages, the initialization-time refcount transitions are not part of the
> observable page lifetime.
>
> This means page_ref_set will no longer observe every initialization-time
> refcount assignment for copied ZONE_DEVICE head pages. The impact is
> controlled because the final initialized struct page state is unchanged,
> and keeping a separate non-template path only for this local tracepoint
> observability would add complexity to the common path.
>
> This patch accelerates head-page initialization. The pfns_per_compound
> == 1 case gets the full benefit here, compound tails are handled in the
> next patch.
>
> Tested in a VM with a 100 GB fsdax namespace device configured with
> map=dev on Intel Ice Lake server. This test exercises the nd_pmem rebind
> path (pfns_per_compound == 1).
>
> Test procedure:
> Rebind the nd_pmem driver 30 times and collect the memmap initialization
> time from the pr_debug() output of memmap_init_zone_device().
>
> Base(v7.3-rc1):
> Average of rebinds for nd_pmem driver: 221.07 ms
>
> With this patch and its prerequisites applied:
> Average of rebinds for nd_pmem driver: 155.00 ms
>
> This reduces the average memmap initialization time measured during
> rebind from 221.07 ms to 155.00 ms, or about 29.9%.
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
With one nit below
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> mm/mm_init.c | 38 +++++++++++++++++++++++++++++++++++---
> 1 file changed, 35 insertions(+), 3 deletions(-)
>
> @@ -1093,10 +1106,29 @@ void __ref memmap_init_zone_device(struct zone *zone,
> nr_pages = end_pfn - start_pfn;
> }
>
> - for (pfn = start_pfn; pfn < end_pfn; pfn += pfns_per_compound) {
> - struct page *page = pfn_to_page(pfn);
> + if (!nr_pages)
> + return;
>
> - __init_zone_device_page(page, pfn, zone_idx, nid, pgmap);
> + /*
> + * Seed the reusable head-page template from the first real struct
> + * page. The normal page-init and refcount helpers must operate on
> + * a real memmap entry rather than a stack object.
> + */
> + pfn = start_pfn;
> + page = pfn_to_page(pfn);
> + __init_zone_device_page(page, pfn, zone_idx, nid, pgmap);
> + memcpy(&template, page, sizeof(*page));
> + if (pfns_per_compound != 1)
> + memmap_init_compound(page, pfn, zone_idx, nid, pgmap,
> + compound_nr_pages(pfn, altmap, pgmap));
> + pfn += pfns_per_compound;
> +
> + /* Initialize the remaining head pages from template. */
> + for (; pfn < end_pfn; pfn += pfns_per_compound) {
> + page = pfn_to_page(pfn);
> +
> + zone_device_page_init_from_template(page, pfn,
> + &template);
Nit: this seems to fit into 80-chars line without wrapping.
>
> if (IS_ALIGNED(pfn, PAGES_PER_SECTION))
> cond_resched();
> --
> 2.20.1
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-09-02 4:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 11:16 [PATCH v11 0/7] mm: optimize zone-device memmap initialization Li Zhe
2026-08-31 11:16 ` [PATCH v11 1/7] mm: fix stale ZONE_DEVICE refcount comment Li Zhe
2026-08-31 11:16 ` [PATCH v11 2/7] mm: add a set_page_section_from_pfn() helper Li Zhe
2026-08-31 11:16 ` [PATCH v11 3/7] mm: add a template-based fast path for zone-device page init Li Zhe
2026-09-02 4:16 ` Mike Rapoport [this message]
2026-09-03 2:58 ` Li Zhe
2026-08-31 11:16 ` [PATCH v11 4/7] mm: extend the template fast path to zone-device compound tails Li Zhe
2026-09-02 4:18 ` Mike Rapoport
2026-08-31 11:16 ` [PATCH v11 5/7] string: introduce memcpy_nontemporal() Li Zhe
2026-08-31 11:16 ` [PATCH v11 6/7] mm: use memcpy_nontemporal() in zone-device template copies Li Zhe
2026-08-31 11:16 ` [PATCH v11 7/7] x86/string: extend memcpy_flushcache() fixed-size fastpaths Li Zhe
2026-08-31 23:45 ` [PATCH v11 0/7] mm: optimize zone-device memmap initialization Andrew Morton
2026-09-01 2:58 ` Li Zhe
2026-09-01 23:07 ` Andrew Morton
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=apejDEdW95T-tekb@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=arnd@arndb.de \
--cc=balbirs@nvidia.com \
--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=muchun.song@linux.dev \
--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