From: libaokun@huaweicloud.com
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.cz,
linux-kernel@vger.kernel.org, kernel@pankajraghav.com,
mcgrof@kernel.org, ebiggers@kernel.org, willy@infradead.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
chengzhihao1@huawei.com, libaokun1@huawei.com,
libaokun@huaweicloud.com, Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH v4 24/24] ext4: enable block size larger than page size
Date: Fri, 21 Nov 2025 17:06:54 +0800 [thread overview]
Message-ID: <20251121090654.631996-25-libaokun@huaweicloud.com> (raw)
In-Reply-To: <20251121090654.631996-1-libaokun@huaweicloud.com>
From: Baokun Li <libaokun1@huawei.com>
Since block device (See commit 3c20917120ce ("block/bdev: enable large
folio support for large logical block sizes")) and page cache (See commit
ab95d23bab220ef8 ("filemap: allocate mapping_min_order folios in the page
cache")) has the ability to have a minimum order when allocating folio,
and ext4 has supported large folio in commit 7ac67301e82f ("ext4: enable
large folio for regular file"), now add support for block_size > PAGE_SIZE
in ext4.
set_blocksize() -> bdev_validate_blocksize() already validates the block
size, so ext4_load_super() does not need to perform additional checks.
Here we only need to add the FS_LBS bit to fs_flags.
In addition, block sizes larger than the page size are currently supported
only when CONFIG_TRANSPARENT_HUGEPAGE is enabled. To make this explicit,
a blocksize_gt_pagesize entry has been added under /sys/fs/ext4/feature/,
indicating whether bs > ps is supported. This allows mke2fs to check the
interface and determine whether a warning should be issued when formatting
a filesystem with block size larger than the page size.
Suggested-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
---
fs/ext4/super.c | 3 ++-
fs/ext4/sysfs.c | 6 ++++++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 3d03a6eb0ea0..87205660c5d0 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -7453,7 +7453,8 @@ static struct file_system_type ext4_fs_type = {
.init_fs_context = ext4_init_fs_context,
.parameters = ext4_param_specs,
.kill_sb = ext4_kill_sb,
- .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP | FS_MGTIME,
+ .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP | FS_MGTIME |
+ FS_LBS,
};
MODULE_ALIAS_FS("ext4");
diff --git a/fs/ext4/sysfs.c b/fs/ext4/sysfs.c
index 987bd00f916a..0018e09b867e 100644
--- a/fs/ext4/sysfs.c
+++ b/fs/ext4/sysfs.c
@@ -332,6 +332,9 @@ EXT4_ATTR_FEATURE(fast_commit);
#if IS_ENABLED(CONFIG_UNICODE) && defined(CONFIG_FS_ENCRYPTION)
EXT4_ATTR_FEATURE(encrypted_casefold);
#endif
+#ifdef CONFIG_TRANSPARENT_HUGEPAGE
+EXT4_ATTR_FEATURE(blocksize_gt_pagesize);
+#endif
static struct attribute *ext4_feat_attrs[] = {
ATTR_LIST(lazy_itable_init),
@@ -351,6 +354,9 @@ static struct attribute *ext4_feat_attrs[] = {
ATTR_LIST(fast_commit),
#if IS_ENABLED(CONFIG_UNICODE) && defined(CONFIG_FS_ENCRYPTION)
ATTR_LIST(encrypted_casefold),
+#endif
+#ifdef CONFIG_TRANSPARENT_HUGEPAGE
+ ATTR_LIST(blocksize_gt_pagesize),
#endif
NULL,
};
--
2.46.1
next prev parent reply other threads:[~2025-11-21 9:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 9:06 [PATCH v4 00/24] " libaokun
2025-11-21 9:06 ` [PATCH v4 01/24] ext4: remove page offset calculation in ext4_block_zero_page_range() libaokun
2025-11-21 9:06 ` [PATCH v4 02/24] ext4: remove page offset calculation in ext4_block_truncate_page() libaokun
2025-11-21 9:06 ` [PATCH v4 03/24] ext4: remove PAGE_SIZE checks for rec_len conversion libaokun
2025-11-21 9:06 ` [PATCH v4 04/24] ext4: make ext4_punch_hole() support large block size libaokun
2025-11-21 9:06 ` [PATCH v4 05/24] ext4: enable DIOREAD_NOLOCK by default for BS > PS as well libaokun
2025-11-21 9:06 ` [PATCH v4 06/24] ext4: introduce s_min_folio_order for future BS > PS support libaokun
2025-11-21 9:06 ` [PATCH v4 07/24] ext4: support large block size in ext4_calculate_overhead() libaokun
2025-11-21 9:06 ` [PATCH v4 08/24] ext4: support large block size in ext4_readdir() libaokun
2025-11-21 9:06 ` [PATCH v4 09/24] ext4: add EXT4_LBLK_TO_B macro for logical block to bytes conversion libaokun
2025-11-21 9:06 ` [PATCH v4 10/24] ext4: add EXT4_LBLK_TO_PG and EXT4_PG_TO_LBLK for block/page conversion libaokun
2025-11-21 9:06 ` [PATCH v4 11/24] ext4: support large block size in ext4_mb_load_buddy_gfp() libaokun
2025-11-21 9:06 ` [PATCH v4 12/24] ext4: support large block size in ext4_mb_get_buddy_page_lock() libaokun
2025-11-21 9:06 ` [PATCH v4 13/24] ext4: support large block size in ext4_mb_init_cache() libaokun
2025-11-21 9:06 ` [PATCH v4 14/24] ext4: prepare buddy cache inode for BS > PS with large folios libaokun
2025-11-21 9:06 ` [PATCH v4 15/24] ext4: rename 'page' references to 'folio' in multi-block allocator libaokun
2025-11-21 9:06 ` [PATCH v4 16/24] ext4: support large block size in ext4_mpage_readpages() libaokun
2025-11-21 9:06 ` [PATCH v4 17/24] ext4: support large block size in ext4_block_write_begin() libaokun
2025-11-21 9:06 ` [PATCH v4 18/24] ext4: support large block size in mpage_map_and_submit_buffers() libaokun
2025-11-21 9:06 ` [PATCH v4 19/24] ext4: support large block size in mpage_prepare_extent_to_map() libaokun
2025-11-21 9:06 ` [PATCH v4 20/24] ext4: support large block size in __ext4_block_zero_page_range() libaokun
2025-11-21 9:06 ` [PATCH v4 21/24] ext4: make data=journal support large block size libaokun
2025-11-21 9:06 ` [PATCH v4 22/24] ext4: support verifying data from large folios with fs-verity libaokun
2025-11-21 9:06 ` [PATCH v4 23/24] ext4: add checks for large folio incompatibilities when BS > PS libaokun
2025-11-21 9:06 ` libaokun [this message]
2025-11-21 10:26 ` [PATCH v4 00/24] ext4: enable block size larger than page size Ojaswin Mujoo
2025-11-22 0:13 ` Baokun Li
2025-12-01 16:23 ` Theodore Ts'o
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=20251121090654.631996-25-libaokun@huaweicloud.com \
--to=libaokun@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=chengzhihao1@huawei.com \
--cc=ebiggers@kernel.org \
--cc=jack@suse.cz \
--cc=kernel@pankajraghav.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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®