From: Wei Yang <richard.weiyang@gmail.com>
To: willy@infradead.org, akpm@linux-foundation.org, david@kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, ziy@nvidia.com, baolin.wang@linux.alibaba.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH] mm/huge_memory: consolidate order-related checks into folio_split_supported()
Date: Fri, 14 Nov 2025 07:57:03 +0000 [thread overview]
Message-ID: <20251114075703.10434-1-richard.weiyang@gmail.com> (raw)
The primary goal of the folio_split_supported() function is to validate
whether a folio is suitable for splitting and to bail out early if it is
not.
Currently, some order-related checks are scattered throughout the
calling code rather than being centralized in folio_split_supported().
This commit moves all remaining order-related validation logic into
folio_split_supported(). This consolidation ensures that the function
serves its intended purpose as a single point of failure and improves
the clarity and maintainability of the surrounding code.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
---
include/linux/pagemap.h | 6 +++
mm/huge_memory.c | 88 +++++++++++++++++++++--------------------
2 files changed, 51 insertions(+), 43 deletions(-)
diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
index 09b581c1d878..d8c8df629b90 100644
--- a/include/linux/pagemap.h
+++ b/include/linux/pagemap.h
@@ -516,6 +516,12 @@ static inline bool mapping_large_folio_support(const struct address_space *mappi
return mapping_max_folio_order(mapping) > 0;
}
+static inline bool
+mapping_folio_order_supported(const struct address_space *mapping, unsigned int order)
+{
+ return (order >= mapping_min_folio_order(mapping) && order <= mapping_max_folio_order(mapping));
+}
+
/* Return the maximum folio size for this pagecache mapping, in bytes. */
static inline size_t mapping_max_folio_size(const struct address_space *mapping)
{
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 0184cd915f44..68faac843527 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -3690,34 +3690,58 @@ static int __split_unmapped_folio(struct folio *folio, int new_order,
bool folio_split_supported(struct folio *folio, unsigned int new_order,
enum split_type split_type, bool warns)
{
+ const int old_order = folio_order(folio);
+
+ if (new_order >= old_order)
+ return -EINVAL;
+
if (folio_test_anon(folio)) {
/* order-1 is not supported for anonymous THP. */
VM_WARN_ONCE(warns && new_order == 1,
"Cannot split to order-1 folio");
if (new_order == 1)
return false;
- } else if (split_type == SPLIT_TYPE_NON_UNIFORM || new_order) {
- if (IS_ENABLED(CONFIG_READ_ONLY_THP_FOR_FS) &&
- !mapping_large_folio_support(folio->mapping)) {
- /*
- * We can always split a folio down to a single page
- * (new_order == 0) uniformly.
- *
- * For any other scenario
- * a) uniform split targeting a large folio
- * (new_order > 0)
- * b) any non-uniform split
- * we must confirm that the file system supports large
- * folios.
- *
- * Note that we might still have THPs in such
- * mappings, which is created from khugepaged when
- * CONFIG_READ_ONLY_THP_FOR_FS is enabled. But in that
- * case, the mapping does not actually support large
- * folios properly.
- */
+ } else {
+ const struct address_space *mapping = NULL;
+
+ mapping = folio->mapping;
+
+ /* Truncated ? */
+ /*
+ * TODO: add support for large shmem folio in swap cache.
+ * When shmem is in swap cache, mapping is NULL and
+ * folio_test_swapcache() is true.
+ */
+ if (!mapping)
+ return false;
+
+ /*
+ * We have two types of split:
+ *
+ * a) uniform split: split folio directly to new_order.
+ * b) non-uniform split: create after-split folios with
+ * orders from (old_order - 1) to new_order.
+ *
+ * For file system, we encodes it supported folio order in
+ * mapping->flags, which could be checked by
+ * mapping_folio_order_supported().
+ *
+ * With these knowledge, we can know whether folio support
+ * split to new_order by:
+ *
+ * 1. check new_order is supported first
+ * 2. check (old_order - 1) is supported if
+ * SPLIT_TYPE_NON_UNIFORM
+ */
+ if (!mapping_folio_order_supported(mapping, new_order)) {
+ VM_WARN_ONCE(warns,
+ "Cannot split file folio to unsupported order: %d", new_order);
+ return false;
+ }
+ if (split_type == SPLIT_TYPE_NON_UNIFORM
+ && !mapping_folio_order_supported(mapping, old_order - 1)) {
VM_WARN_ONCE(warns,
- "Cannot split file folio to non-0 order");
+ "Cannot split file folio to unsupported order: %d", old_order - 1);
return false;
}
}
@@ -3785,9 +3809,6 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
if (folio != page_folio(split_at) || folio != page_folio(lock_at))
return -EINVAL;
- if (new_order >= old_order)
- return -EINVAL;
-
if (!folio_split_supported(folio, new_order, split_type, /* warn = */ true))
return -EINVAL;
@@ -3819,28 +3840,9 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
}
mapping = NULL;
} else {
- unsigned int min_order;
gfp_t gfp;
mapping = folio->mapping;
-
- /* Truncated ? */
- /*
- * TODO: add support for large shmem folio in swap cache.
- * When shmem is in swap cache, mapping is NULL and
- * folio_test_swapcache() is true.
- */
- if (!mapping) {
- ret = -EBUSY;
- goto out;
- }
-
- min_order = mapping_min_folio_order(folio->mapping);
- if (new_order < min_order) {
- ret = -EINVAL;
- goto out;
- }
-
gfp = current_gfp_context(mapping_gfp_mask(mapping) &
GFP_RECLAIM_MASK);
--
2.34.1
next reply other threads:[~2025-11-14 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 7:57 Wei Yang [this message]
2025-11-14 8:49 ` [PATCH] mm/huge_memory: consolidate order-related checks into folio_split_supported() David Hildenbrand (Red Hat)
2025-11-14 12:43 ` Zi Yan
2025-11-14 14:30 ` Wei Yang
2025-11-14 20:53 ` Zi Yan
2025-11-15 2:42 ` Wei Yang
2025-11-14 15:03 ` Wei Yang
2025-11-14 19:36 ` David Hildenbrand (Red Hat)
2025-11-15 2:51 ` Wei Yang
2025-11-15 5:07 ` Matthew Wilcox
2025-11-15 9:43 ` Wei Yang
2025-12-04 15:13 ` Wei Yang
2025-11-19 12:37 ` Dan Carpenter
2025-11-19 12:39 ` Wei Yang
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=20251114075703.10434-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--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