From: "Li Zhe" <lizhe.67@bytedance.com>
To: <apopple@nvidia.com>
Cc: <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>,
<lizhe.67@bytedance.com>, <mingo@redhat.com>, <rppt@kernel.org>,
<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 14:36:29 +0800 [thread overview]
Message-ID: <20260707063629.40360-1-lizhe.67@bytedance.com> (raw)
In-Reply-To: <akxsbwyfYH1LCyGm@nvdebian.thelocal>
On Tue, 7 Jul 2026 13:06:02 +1000, apopple@nvidia.com wrote:
> > > 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.
Thanks. I will keep this series focused on the pmem-oriented
ZONE_DEVICE path for now, and I will report back separately if the
follow-up work on normal page initialization turns up anything useful,
positive or negative.
Thanks,
Zhe
next prev parent reply other threads:[~2026-07-07 6:36 UTC|newest]
Thread overview: 42+ 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
2026-07-07 6:36 ` Li Zhe [this message]
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-02 2:16 ` Borislav Petkov
2026-07-02 7:36 ` 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-02 2:23 ` Borislav Petkov
2026-07-02 7:37 ` Li Zhe
2026-07-03 19:56 ` Borislav Petkov
2026-07-06 7:43 ` Li Zhe
2026-07-06 17:19 ` Borislav Petkov
2026-07-07 11:34 ` Li Zhe
2026-07-01 9:05 ` [PATCH v5 8/8] mm: use memcpy_nt() in zone-device template copies Li Zhe
2026-07-01 23:28 ` [PATCH v5 0/8] mm: optimize zone-device memmap initialization Andrew Morton
2026-07-02 2:24 ` Borislav Petkov
2026-07-02 7:39 ` 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=20260707063629.40360-1-lizhe.67@bytedance.com \
--to=lizhe.67@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--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=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