]> git.ipfire.org Git - thirdparty/linux.git/commit
ext4: use optimized mballoc scanning regardless of inode format
authorJan Kara <jack@suse.cz>
Wed, 14 Jan 2026 18:28:19 +0000 (19:28 +0100)
committerTheodore Ts'o <tytso@mit.edu>
Tue, 20 Jan 2026 03:54:58 +0000 (22:54 -0500)
commit3574c322b1d0eb32dbd76b469cb08f9a67641599
tree45cf4b9fef6a25bceacf46448080be110beea6af
parent4865c768b563deff1b6a6384e74a62f143427b42
ext4: use optimized mballoc scanning regardless of inode format

Currently we don't used mballoc optimized scanning (using max free
extent order and avg free extent order group lists) for inodes with
indirect block based format. This is confusing for users and I don't see
a good reason for that. Even with indirect block based inode format we
can spend big amount of time searching for free blocks for large
filesystems with fragmented free space. To add to the confusion before
commit 077d0c2c78df ("ext4: make mb_optimize_scan performance mount
option work with extents") optimized scanning was applied *only* to
indirect block based inodes so that commit appears as a performance
regression to some users. Just use optimized scanning whenever it is
enabled by mount options.

Reviewed-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Cc: stable@kernel.org
Link: https://patch.msgid.link/20260114182836.14120-4-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/ext4/mballoc.c