From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, Baokun Li <libaokun1@huawei.com>,
Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2 v2] ext4: use mb_optimize_scan regardless of inode format
Date: Fri, 9 Jan 2026 11:53:36 +0100 [thread overview]
Message-ID: <20260109105007.27673-1-jack@suse.cz> (raw)
Hello,
this patch series enables use of mballoc optimizations regardless of the inode
format. See patch 2 for details.
Changes since v1:
* Added patch to make sure mballoc doesn't select group with block numbers
greater than 2^32 for indirect block based inodes
Previous versions:
v1: https://lore.kernel.org/all/20260108160907.24892-2-jack@suse.cz/
Honza
next reply other threads:[~2026-01-09 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 10:53 Jan Kara [this message]
2026-01-09 10:53 ` [PATCH 1/2] ext4: always allocate blocks only from groups inode can use Jan Kara
2026-01-10 0:59 ` Baokun Li
2026-01-10 1:36 ` Zhang Yi
2026-01-13 16:28 ` Pedro Falcato
2026-01-14 17:26 ` Jan Kara
2026-01-09 10:53 ` [PATCH 2/2] ext4: use optimized mballoc scanning regardless of inode format Jan Kara
2026-01-10 1:00 ` Baokun Li
2026-01-10 1:38 ` Zhang Yi
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=20260109105007.27673-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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