From: Qi Zheng <qi.zheng@linux.dev>
To: muchun.song@linux.dev, osalvador@suse.de, david@kernel.org,
akpm@linux-foundation.org, azpijr@gmail.com,
lance.yang@linux.dev
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: [PATCH v2 0/4] mm: hugetlb: fix CMA-related issues
Date: Thu, 5 Nov 2026 12:07:42 +0800 [thread overview]
Message-ID: <cover.1793850539.git.zhengqi.arch@bytedance.com> (raw)
From: Qi Zheng <zhengqi.arch@bytedance.com>
Hi all,
This series fixes four CMA-related issues in HugeTLB reservation,
long-term pinning and allocation:
- Avoid ineffective CMA reservations on 32-bit x86 kernels running on
CPUs that advertise 1 GiB page support.
- Allow long-term pins of explicitly CMA-allocated HugeTLB folios,
which already own their CMA bitmap ranges.
- Preserve the caller's GFP mask when allocating from CMA.
- Enforce cpuset restrictions on gigantic surplus allocations while
preserving memory policy semantics.
Changes in v2:
- Replace the PF_MEMALLOC_PIN allocation restriction with a GUP exception
for HugeTLB folios marked HPG_cma. (suggested by Muchun Song)
- Pass the caller's GFP mask through cma_alloc_frozen_compound() instead
of skipping CMA when direct reclaim is disallowed.
(suggested by sashiko)
- Remove unnecessary revalidation of successfully allocated folios after
cpuset changes. Retry only failed allocations.
(pointed by Jose A. Perez de Azpillaga)
- collect Reviewed-by and Acked-by.
- Rebase onto next-20261104.
Qi Zheng (4):
x86: hugetlb: disable default CMA reservations on 32-bit kernel
mm: gup: allow long-term pins of CMA-allocated HugeTLB folios
mm: hugetlb: fix GFP mask propagation to CMA
mm: hugetlb: fix cpuset violations in gigantic surplus allocations
arch/x86/mm/hugetlbpage.c | 2 +-
include/linux/cma.h | 2 +-
include/linux/mm.h | 29 +----------------------------
mm/cma.c | 4 ++--
mm/gup.c | 31 +++++++++++++++++++++++++++++++
mm/hugetlb.c | 25 ++++++++++++++++++-------
mm/hugetlb_cma.c | 4 ++--
7 files changed, 56 insertions(+), 41 deletions(-)
base-commit: 8b7179210b22f8e48a82c5ceacb9d56a9c4cfec4
--
2.54.0
next reply other threads:[~2026-11-05 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 4:07 Qi Zheng [this message]
2026-11-05 4:07 ` [PATCH v2 1/4] x86: hugetlb: disable default CMA reservations on 32-bit kernel Qi Zheng
2026-11-05 9:29 ` Oscar Salvador (SUSE)
2026-11-05 4:07 ` [PATCH v2 2/4] mm: gup: allow long-term pins of CMA-allocated HugeTLB folios Qi Zheng
2026-11-05 5:13 ` Muchun Song
2026-11-06 2:48 ` Qi Zheng
2026-11-06 2:54 ` Muchun Song
2026-11-05 9:33 ` Oscar Salvador (SUSE)
2026-11-05 11:28 ` Jose A. Perez de Azpillaga
2026-11-05 4:07 ` [PATCH v2 3/4] mm: hugetlb: fix GFP mask propagation to CMA Qi Zheng
2026-11-05 5:17 ` Muchun Song
2026-11-05 10:00 ` Oscar Salvador (SUSE)
2026-11-06 2:43 ` Qi Zheng
2026-11-06 5:50 ` Oscar Salvador (SUSE)
2026-11-05 11:28 ` Jose A. Perez de Azpillaga
2026-11-05 4:07 ` [PATCH v2 4/4] mm: hugetlb: fix cpuset violations in gigantic surplus allocations Qi Zheng
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=cover.1793850539.git.zhengqi.arch@bytedance.com \
--to=qi.zheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=azpijr@gmail.com \
--cc=david@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=zhengqi.arch@bytedance.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
all inboxes | Powered by JetHome®