From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Muchun Song <muchun.song@linux.dev>
Cc: <sidhartha.kumar@oracle.com>, <jane.chu@oracle.com>,
Zi Yan <ziy@nvidia.com>, Vlastimil Babka <vbabka@suse.cz>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, <linux-mm@kvack.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v3 0/6] mm: hugetlb: allocate frozen gigantic folio
Date: Mon, 13 Oct 2025 21:38:48 +0800 [thread overview]
Message-ID: <20251013133854.2466530-1-wangkefeng.wang@huawei.com> (raw)
Introduce alloc_contig_frozen_pages() and cma_alloc_frozen_compound()
which avoid atomic operation about page refcount, and then convert to
allocate frozen gigantic folio by the new helpers in hugetlb to cleanup
the alloc_gigantic_folio().
v3:
- Fix built warn/err, found by lkp test
- Address some David's comments,
- Force on frozen part and drop the optimization part
- Rename split_non_compound_pages() to __split_pages()
- Adding back debug print/WARN_ON if no cma range found or the
pfn range of page is not full match the cma range.
v2:
- Optimize gigantic folio allocation speed
- Using HPAGE_PUD_ORDER in debug_vm_pgtable
- Address some David's comments,
- kill folio_alloc_gigantic()
- add generic cma_alloc_frozen{_compound}() instead of
cma_{alloc,free}_folio
Kefeng Wang (6):
mm: debug_vm_pgtable: add debug_vm_pgtable_free_huge_page()
mm: page_alloc: add __split_page()
mm: page_alloc: add alloc_contig_{range_frozen,frozen_pages}()
mm: cma: add __cma_release()
mm: cma: add cma_alloc_frozen{_compound}()
mm: hugetlb: allocate frozen pages in alloc_gigantic_folio()
include/linux/cma.h | 26 ++----
include/linux/gfp.h | 52 +++++------
mm/cma.c | 109 +++++++++++-----------
mm/debug_vm_pgtable.c | 38 ++++----
mm/hugetlb.c | 58 +++---------
mm/hugetlb_cma.c | 27 +++---
mm/hugetlb_cma.h | 10 +--
mm/internal.h | 6 ++
mm/page_alloc.c | 204 ++++++++++++++++++++++++++++--------------
9 files changed, 271 insertions(+), 259 deletions(-)
--
2.27.0
next reply other threads:[~2025-10-13 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 13:38 Kefeng Wang [this message]
2025-10-13 13:38 ` [PATCH v3 1/6] mm: debug_vm_pgtable: add debug_vm_pgtable_free_huge_page() Kefeng Wang
2025-10-13 13:38 ` [PATCH v3 2/6] mm: page_alloc: add __split_page() Kefeng Wang
2025-10-13 19:44 ` David Hildenbrand
2025-10-14 3:45 ` Kefeng Wang
2025-10-13 13:38 ` [PATCH v3 3/6] mm: page_alloc: add alloc_contig_{range_frozen,frozen_pages}() Kefeng Wang
2025-10-16 20:53 ` David Hildenbrand
2025-10-17 7:19 ` Kefeng Wang
2025-10-20 13:07 ` David Hildenbrand
2025-10-20 15:21 ` Kefeng Wang
2025-10-23 12:06 ` Kefeng Wang
2025-10-13 13:38 ` [PATCH v3 4/6] mm: cma: add __cma_release() Kefeng Wang
2025-10-13 19:48 ` David Hildenbrand
2025-10-14 3:45 ` Kefeng Wang
2025-10-13 13:38 ` [PATCH v3 5/6] mm: cma: add cma_alloc_frozen{_compound}() Kefeng Wang
2025-10-13 13:38 ` [PATCH v3 6/6] mm: hugetlb: allocate frozen pages in alloc_gigantic_folio() Kefeng Wang
2025-10-16 1:20 ` [PATCH v3 0/6] mm: hugetlb: allocate frozen gigantic folio Kefeng Wang
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=20251013133854.2466530-1-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=jane.chu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=sidhartha.kumar@oracle.com \
--cc=vbabka@suse.cz \
--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