From: Zhang Yi <yi.zhang@huaweicloud.com>
To: linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.cz,
ritesh.list@gmail.com, yi.zhang@huawei.com,
yi.zhang@huaweicloud.com, chengzhihao1@huawei.com,
yukuai3@huawei.com
Subject: [PATCH 00/10] ext4: simplify the counting and management of delalloc reserved blocks
Date: Sat, 1 Jun 2024 11:41:39 +0800 [thread overview]
Message-ID: <20240601034149.2169771-1-yi.zhang@huaweicloud.com> (raw)
From: Zhang Yi <yi.zhang@huawei.com>
Hello!
This patch series is the part 3 prepartory changes of the buffered IO
iomap conversion, it simplify the counting and updating logic of delalloc
reserved blocks. I picked them out from my buffered IO iomap conversion
RFC series v4[1], and did some minor change log messages improvement.
It's based on the part 2 prepartory series [2] (not merged yet) +
6.10-rc1.
Patch 1-3 simplify the delalloc extent management logic by changes to
always set EXT4_GET_BLOCKS_DELALLOC_RESERVE flag when allocating
preallocated blocks, and don't add EXTENT_STATUS_DELAYED flag to an
unwritten extent, which means ext4_es_is_delayed() is equal to
ext4_es_is_delonly().
Patch 4-6 simplify the reserved blocks updating logic by moves the
reserved blocks updating from ext4_{ind|ext}_map_blocks() to
ext4_es_insert_extent().
Patch 7-10 drop the unused code (e.g. ext4_es_is_delonly())and update
comments.
This series has passed through kvm-xfstests in auto mode many times,
please take a look at it.
[1] https://lore.kernel.org/linux-ext4/20240410142948.2817554-1-yi.zhang@huaweicloud.com/
[2] https://lore.kernel.org/linux-ext4/20240517124005.347221-1-yi.zhang@huaweicloud.com/
Thanks,
Yi.
Zhang Yi (10):
ext4: factor out ext4_map_create_blocks() to allocate new blocks
ext4: optimize the EXT4_GET_BLOCKS_DELALLOC_RESERVE flag set
ext4: don't set EXTENT_STATUS_DELAYED on allocated blocks
ext4: let __revise_pending() return newly inserted pendings
ext4: count removed reserved blocks for delalloc only extent entry
ext4: update delalloc data reserve spcae in ext4_es_insert_extent()
ext4: drop ext4_es_delayed_clu()
ext4: use ext4_map_query_blocks() in ext4_map_blocks()
ext4: drop ext4_es_is_delonly()
ext4: drop all delonly descriptions
fs/ext4/extents.c | 37 ------
fs/ext4/extents_status.c | 271 ++++++++++++++++-----------------------
fs/ext4/extents_status.h | 7 -
fs/ext4/indirect.c | 7 -
fs/ext4/inode.c | 197 +++++++++++++---------------
5 files changed, 195 insertions(+), 324 deletions(-)
--
2.31.1
next reply other threads:[~2024-06-01 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 3:41 Zhang Yi [this message]
2024-06-01 3:41 ` [PATCH 01/10] ext4: factor out ext4_map_create_blocks() to allocate new blocks Zhang Yi
2024-06-01 3:41 ` [PATCH 02/10] ext4: optimize the EXT4_GET_BLOCKS_DELALLOC_RESERVE flag set Zhang Yi
2024-06-01 3:41 ` [PATCH 03/10] ext4: don't set EXTENT_STATUS_DELAYED on allocated blocks Zhang Yi
2024-06-01 3:41 ` [PATCH 04/10] ext4: let __revise_pending() return newly inserted pendings Zhang Yi
2024-06-01 3:41 ` [PATCH 05/10] ext4: count removed reserved blocks for delalloc only extent entry Zhang Yi
2024-06-01 3:41 ` [PATCH 06/10] ext4: update delalloc data reserve spcae in ext4_es_insert_extent() Zhang Yi
2024-06-01 3:41 ` [PATCH 07/10] ext4: drop ext4_es_delayed_clu() Zhang Yi
2024-06-01 3:41 ` [PATCH 08/10] ext4: use ext4_map_query_blocks() in ext4_map_blocks() Zhang Yi
2024-06-01 3:41 ` [PATCH 09/10] ext4: drop ext4_es_is_delonly() Zhang Yi
2024-06-01 3:41 ` [PATCH 10/10] ext4: drop all delonly descriptions 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=20240601034149.2169771-1-yi.zhang@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=chengzhihao1@huawei.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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;
as well as URLs for NNTP newsgroup(s).