From: David Hildenbrand <david@redhat.com>
To: Balbir Singh <balbirs@nvidia.com>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Zi Yan" <ziy@nvidia.com>,
"Joshua Hahn" <joshua.hahnjy@gmail.com>,
"Rakie Kim" <rakie.kim@sk.com>,
"Byungchul Park" <byungchul@sk.com>,
"Gregory Price" <gourry@gourry.net>,
"Ying Huang" <ying.huang@linux.alibaba.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Oscar Salvador" <osalvador@suse.de>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Nico Pache" <npache@redhat.com>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Dev Jain" <dev.jain@arm.com>, "Barry Song" <baohua@kernel.org>,
"Lyude Paul" <lyude@redhat.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Ralph Campbell" <rcampbell@nvidia.com>,
"Mika Penttilä" <mpenttil@redhat.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Francois Dugast" <francois.dugast@intel.com>
Subject: Re: [v3 01/11] mm/zone_device: support large zone device private folios
Date: Tue, 26 Aug 2025 16:22:39 +0200 [thread overview]
Message-ID: <54bfb6c0-eb35-4e53-ab45-04139623abb0@redhat.com> (raw)
In-Reply-To: <20250812024036.690064-2-balbirs@nvidia.com>
On 12.08.25 04:40, Balbir Singh wrote:
> Add routines to support allocation of large order zone device folios
> and helper functions for zone device folios, to check if a folio is
> device private and helpers for setting zone device data.
>
> When large folios are used, the existing page_free() callback in
> pgmap is called when the folio is freed, this is true for both
> PAGE_SIZE and higher order pages.
>
> Zone device private large folios do not support deferred split and
> scan like normal THP folios.
[...]
> #else
> static inline void *devm_memremap_pages(struct device *dev,
> struct dev_pagemap *pgmap)
> diff --git a/mm/memremap.c b/mm/memremap.c
> index b0ce0d8254bd..13e87dd743ad 100644
> --- a/mm/memremap.c
> +++ b/mm/memremap.c
> @@ -427,20 +427,19 @@ EXPORT_SYMBOL_GPL(get_dev_pagemap);
> void free_zone_device_folio(struct folio *folio)
> {
> struct dev_pagemap *pgmap = folio->pgmap;
> + unsigned long nr = folio_nr_pages(folio);
> + int i;
Not that it will currently matter much but
unsigned long i, nr = folio_nr_pages(folio);
might be more consistent
>
> if (WARN_ON_ONCE(!pgmap))
> return;
>
> mem_cgroup_uncharge(folio);
>
> - /*
> - * Note: we don't expect anonymous compound pages yet. Once supported
> - * and we could PTE-map them similar to THP, we'd have to clear
> - * PG_anon_exclusive on all tail pages.
> - */
> if (folio_test_anon(folio)) {
> - VM_BUG_ON_FOLIO(folio_test_large(folio), folio);
> - __ClearPageAnonExclusive(folio_page(folio, 0));
> + for (i = 0; i < nr; i++)
> + __ClearPageAnonExclusive(folio_page(folio, i));
> + } else {
> + VM_WARN_ON_ONCE(folio_test_large(folio));
> }
>
> /*
> @@ -464,11 +463,15 @@ void free_zone_device_folio(struct folio *folio)
>
> switch (pgmap->type) {
> case MEMORY_DEVICE_PRIVATE:
Why are you effectively dropping the
if (WARN_ON_ONCE(!pgmap->ops || !pgmap->ops->page_free))
> + percpu_ref_put_many(&folio->pgmap->ref, nr);
> + pgmap->ops->page_free(&folio->page);
> + folio->page.mapping = NULL;
Why are we adding this here? Does not seem large-folio specific.
> + break;
> case MEMORY_DEVICE_COHERENT:
> if (WARN_ON_ONCE(!pgmap->ops || !pgmap->ops->page_free))
> break;
> - pgmap->ops->page_free(folio_page(folio, 0));
> - put_dev_pagemap(pgmap);
> + pgmap->ops->page_free(&folio->page);
> + percpu_ref_put(&folio->pgmap->ref);
This looks like an independent change that does not belong in this patch.
Can't you just leave the code as is and simply convert percpu_ref_put
to percpu_ref_put_many()? What am I missing?
> break;
>
> case MEMORY_DEVICE_GENERIC:
> @@ -491,14 +494,23 @@ void free_zone_device_folio(struct folio *folio)
> }
> }
>
> -void zone_device_page_init(struct page *page)
> +void zone_device_folio_init(struct folio *folio, unsigned int order)
> {
> + struct page *page = folio_page(folio, 0);
> +
> + VM_WARN_ON_ONCE(order > MAX_ORDER_NR_PAGES);
order vs. pages is wrong.
In context of [1] this should probably be
VM_WARN_ON_ONCE(order > MAX_FOLIO_ORDER);
And before that is in
VM_WARN_ON_ONCE((1u << order) > MAX_FOLIO_NR_PAGES);
because we don't involve the buddy, so likely buddy limits do not apply.
[1] https://lore.kernel.org/all/20250821200701.1329277-1-david@redhat.com/
> +
> /*
> * Drivers shouldn't be allocating pages after calling
> * memunmap_pages().
> */
> - WARN_ON_ONCE(!percpu_ref_tryget_live(&page_pgmap(page)->ref));
> - set_page_count(page, 1);
> + WARN_ON_ONCE(!percpu_ref_tryget_many(&page_pgmap(page)->ref, 1 << order));
> + folio_set_count(folio, 1);
> lock_page(page);
> +
> + if (order > 1) {
> + prep_compound_page(page, order);
> + folio_set_large_rmappable(folio);
> + }
> }
> -EXPORT_SYMBOL_GPL(zone_device_page_init);
> +EXPORT_SYMBOL_GPL(zone_device_folio_init);
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 568198e9efc2..b5837075b6e0 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1769,9 +1769,13 @@ static __always_inline void __folio_remove_rmap(struct folio *folio,
> * the folio is unmapped and at least one page is still mapped.
> *
> * Check partially_mapped first to ensure it is a large folio.
> + *
> + * Device private folios do not support deferred splitting and
> + * shrinker based scanning of the folios to free.
> */
> if (partially_mapped && folio_test_anon(folio) &&
> - !folio_test_partially_mapped(folio))
> + !folio_test_partially_mapped(folio) &&
> + !folio_is_device_private(folio))
Please indent like the previous line.
if (partially_mapped && folio_test_anon(folio) &&
!folio_test_partially_mapped(folio) &&
!folio_is_device_private(folio))
> deferred_split_folio(folio, true);
>
> __folio_mod_stat(folio, -nr, -nr_pmdmapped);
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-08-26 14:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 2:40 [v3 00/11] mm: support device-private THP Balbir Singh
2025-08-12 2:40 ` [v3 01/11] mm/zone_device: support large zone device private folios Balbir Singh
2025-08-26 14:22 ` David Hildenbrand [this message]
2025-08-12 2:40 ` [v3 02/11] mm/thp: zone_device awareness in THP handling code Balbir Singh
2025-08-12 14:47 ` kernel test robot
2025-08-26 15:19 ` David Hildenbrand
2025-08-27 10:14 ` Balbir Singh
2025-08-27 11:28 ` David Hildenbrand
2025-08-28 20:05 ` Matthew Brost
2025-08-28 20:12 ` David Hildenbrand
2025-08-28 20:17 ` Matthew Brost
2025-08-28 20:22 ` David Hildenbrand
2025-08-12 2:40 ` [v3 03/11] mm/migrate_device: THP migration of zone device pages Balbir Singh
2025-08-12 5:35 ` Mika Penttilä
2025-08-12 5:54 ` Matthew Brost
2025-08-12 6:18 ` Matthew Brost
2025-08-12 6:25 ` Mika Penttilä
2025-08-12 6:33 ` Matthew Brost
2025-08-12 6:37 ` Mika Penttilä
2025-08-12 23:36 ` Balbir Singh
2025-08-13 0:07 ` Mika Penttilä
2025-08-14 22:51 ` Balbir Singh
2025-08-15 0:04 ` Matthew Brost
2025-08-15 12:09 ` Balbir Singh
2025-08-21 10:24 ` Balbir Singh
2025-08-28 23:14 ` Matthew Brost
2025-08-12 2:40 ` [v3 04/11] mm/memory/fault: add support for zone device THP fault handling Balbir Singh
2025-08-12 2:40 ` [v3 05/11] lib/test_hmm: test cases and support for zone device private THP Balbir Singh
2025-08-12 2:40 ` [v3 06/11] mm/memremap: add folio_split support Balbir Singh
2025-08-12 2:40 ` [v3 07/11] mm/thp: add split during migration support Balbir Singh
2025-08-27 20:29 ` David Hildenbrand
2025-08-12 2:40 ` [v3 08/11] lib/test_hmm: add test case for split pages Balbir Singh
2025-08-12 2:40 ` [v3 09/11] selftests/mm/hmm-tests: new tests for zone device THP migration Balbir Singh
2025-08-12 2:40 ` [v3 10/11] gpu/drm/nouveau: add THP migration support Balbir Singh
2025-08-13 2:23 ` kernel test robot
2025-08-12 2:40 ` [v3 11/11] selftests/mm/hmm-tests: new throughput tests including THP Balbir Singh
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=54bfb6c0-eb35-4e53-ab45-04139623abb0@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=byungchul@sk.com \
--cc=dakr@kernel.org \
--cc=dev.jain@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lyude@redhat.com \
--cc=matthew.brost@intel.com \
--cc=mpenttil@redhat.com \
--cc=npache@redhat.com \
--cc=osalvador@suse.de \
--cc=rakie.kim@sk.com \
--cc=rcampbell@nvidia.com \
--cc=ryan.roberts@arm.com \
--cc=simona@ffwll.ch \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/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