From: Muchun Song <muchun.song@linux.dev>
To: Li Zhe <lizhe.67@bytedance.com>
Cc: linux-arch@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
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,
rppt@kernel.org, tglx@kernel.org
Subject: Re: [PATCH v6 2/8] mm: factor zone-device page init helpers out of __init_zone_device_page
Date: Tue, 14 Jul 2026 10:44:47 +0800 [thread overview]
Message-ID: <993afd58-e503-46aa-acaf-19243b0d147c@linux.dev> (raw)
In-Reply-To: <20260709112520.24857-3-lizhe.67@bytedance.com>
On 2026/7/9 19:25, Li Zhe wrote:
> memmap_init_zone_device() currently mixes refcount policy and core
> ZONE_DEVICE page setup in a single helper.
>
> Factor the refcount-reset predicate into pagemap_resets_refcount(), move
> the common page initialization into __zone_device_page_init(), and wrap
> the existing slow path in zone_device_page_init_slow().
Hi,
Sorry if this has been discussed before, but I'm still curious—what
is the significance of the 'slow' suffix here? I don't think I quite
understand why this is called the 'slow path' here. Is there also a
'fast path' for initializing struct page?
Thanks.
>
> This keeps the slow-path behaviour unchanged and gives later patches
> reusable helper boundaries.
>
> No functional change intended.
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> mm/mm_init.c | 56 ++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 37 insertions(+), 19 deletions(-)
>
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index 95808ab5cfdb..5fccfbacf855 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -1005,11 +1005,37 @@ static void __init memmap_init(void)
> }
>
> #ifdef CONFIG_ZONE_DEVICE
> -static void __ref __init_zone_device_page(struct page *page, unsigned long pfn,
> +/*
> + * Return true when the free path for this pagemap type restores the page
> + * refcount to 1, so memmap_init_zone_device() can keep the count set by
> + * __init_single_page(). Otherwise initialize the refcount to 0 and leave
> + * it to the allocator or pgmap callbacks to raise it when the page is
> + * handed out again.
> + */
> +static inline bool pagemap_resets_refcount(const struct dev_pagemap *pgmap)
> +{
> + /*
> + * MEMORY_DEVICE_GENERIC pages regain a refcount of 1 in the free
> + * path. The remaining ZONE_DEVICE types start from 0 here and raise
> + * the count again when the allocator or driver hands the page out.
> + */
> + switch (pgmap->type) {
> + case MEMORY_DEVICE_FS_DAX:
> + case MEMORY_DEVICE_PRIVATE:
> + case MEMORY_DEVICE_COHERENT:
> + case MEMORY_DEVICE_PCI_P2PDMA:
> + return false;
> + case MEMORY_DEVICE_GENERIC:
> + return true;
> + }
> +
> + return true;
> +}
> +
> +static void __ref __zone_device_page_init(struct page *page, unsigned long pfn,
> unsigned long zone_idx, int nid,
> struct dev_pagemap *pgmap)
> {
> -
> __init_single_page(page, pfn, zone_idx, nid);
>
> /*
> @@ -1028,23 +1054,15 @@ static void __ref __init_zone_device_page(struct page *page, unsigned long pfn,
> */
> page_folio(page)->pgmap = pgmap;
> page->zone_device_data = NULL;
> +}
>
> - /*
> - * MEMORY_DEVICE_GENERIC pages regain a refcount of 1 in the free
> - * path. The remaining ZONE_DEVICE types start from 0 here and raise
> - * the count again when the allocator or driver hands the page out.
> - */
> - switch (pgmap->type) {
> - case MEMORY_DEVICE_FS_DAX:
> - case MEMORY_DEVICE_PRIVATE:
> - case MEMORY_DEVICE_COHERENT:
> - case MEMORY_DEVICE_PCI_P2PDMA:
> +static void __ref zone_device_page_init_slow(struct page *page,
> + unsigned long pfn, unsigned long zone_idx, int nid,
> + struct dev_pagemap *pgmap)
> +{
> + __zone_device_page_init(page, pfn, zone_idx, nid, pgmap);
> + if (!pagemap_resets_refcount(pgmap))
> set_page_count(page, 0);
> - break;
> -
> - case MEMORY_DEVICE_GENERIC:
> - break;
> - }
> }
>
> /*
> @@ -1090,7 +1108,7 @@ static void __ref memmap_init_compound(struct page *head,
> for (pfn = head_pfn + 1; pfn < end_pfn; pfn++) {
> struct page *page = pfn_to_page(pfn);
>
> - __init_zone_device_page(page, pfn, zone_idx, nid, pgmap);
> + zone_device_page_init_slow(page, pfn, zone_idx, nid, pgmap);
> prep_compound_tail(page, head, order);
> set_page_count(page, 0);
> }
> @@ -1126,7 +1144,7 @@ void __ref memmap_init_zone_device(struct zone *zone,
> for (pfn = start_pfn; pfn < end_pfn; pfn += pfns_per_compound) {
> struct page *page = pfn_to_page(pfn);
>
> - __init_zone_device_page(page, pfn, zone_idx, nid, pgmap);
> + zone_device_page_init_slow(page, pfn, zone_idx, nid, pgmap);
>
> if (IS_ALIGNED(pfn, PAGES_PER_SECTION))
> cond_resched();
> --
> 2.20.1
next prev parent reply other threads:[~2026-07-14 2:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:25 [PATCH v6 0/8] mm: optimize zone-device memmap initialization Li Zhe
2026-07-09 11:25 ` [PATCH v6 1/8] mm: fix stale ZONE_DEVICE refcount comment Li Zhe
2026-07-14 2:25 ` Muchun Song
2026-07-09 11:25 ` [PATCH v6 2/8] mm: factor zone-device page init helpers out of __init_zone_device_page Li Zhe
2026-07-14 2:44 ` Muchun Song [this message]
2026-07-09 11:25 ` [PATCH v6 3/8] mm: add a set_page_section_from_pfn() helper Li Zhe
2026-07-14 2:45 ` Muchun Song
2026-07-09 11:25 ` [PATCH v6 4/8] mm: add a template-based fast path for zone-device page init Li Zhe
2026-07-13 13:28 ` Muchun Song
2026-07-09 11:25 ` [PATCH v6 5/8] mm: extend the template fast path to zone-device compound tails Li Zhe
2026-07-09 11:25 ` [PATCH v6 6/8] string: introduce memcpy_nt() helpers Li Zhe
2026-07-09 11:25 ` [PATCH v6 7/8] x86/string: extend memcpy_flushcache() fixed-size fastpaths Li Zhe
2026-07-09 11:25 ` [PATCH v6 8/8] mm: use memcpy_nt() in zone-device template copies Li Zhe
2026-07-13 1:44 ` [PATCH v6 0/8] mm: optimize zone-device memmap initialization Balbir Singh
2026-07-13 3:18 ` ByteDance
2026-07-13 13:15 ` Muchun Song
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=993afd58-e503-46aa-acaf-19243b0d147c@linux.dev \
--to=muchun.song@linux.dev \
--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=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