From: Ritesh Harjani <riteshh@linux.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: adilger.kernel@dilger.ca, jack@suse.cz, tytso@mit.edu,
mbobrowski@mbobrowski.org, linux-fsdevel@vger.kernel.org,
Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [RFC 0/2] ext4: bmap & fiemap conversion to use iomap
Date: Tue, 20 Aug 2019 18:36:32 +0530 [thread overview]
Message-ID: <20190820130634.25954-1-riteshh@linux.ibm.com> (raw)
Hello,
These are RFC patches to get community view on converting
ext4 bmap & fiemap to iomap infrastructure. This reduces the users
of ext4_get_block API and thus a step towards getting rid of
buffer_heads from ext4. Also reduces the line of code by making
use of iomap infrastructure (ex4_iomap_begin) which is already
used for other operations.
This gets rid of special implementation of ext4_fill_fiemap_extents
& ext4_find_delayed_extent and thus only relies upon ext4_map_blocks
& iomap_fiemap (ext4_iomap_begin) for mapping. It looked more logical
thing to do, but I appreciate if anyone has any review/feedback
comments about this part.
Didn't get any regression on some basic xfstests in tests/ext4/
with mkfs option of "-b 4096". Please let me know if I should also test
any special configurations?
Patches can be cleanly applied over Linux 5.3-rc5.
Ritesh Harjani (2):
ext4: Move ext4 bmap to use iomap infrastructure.
ext4: Move ext4_fiemap to iomap infrastructure
fs/ext4/extents.c | 294 +++++++---------------------------------------
fs/ext4/inline.c | 41 -------
fs/ext4/inode.c | 17 ++-
3 files changed, 53 insertions(+), 299 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-20 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 13:06 Ritesh Harjani [this message]
2019-08-20 13:06 ` [RFC 1/2] ext4: Move ext4 bmap to use iomap infrastructure Ritesh Harjani
2019-10-16 8:31 ` Jan Kara
2019-10-16 12:35 ` Ritesh Harjani
2019-08-20 13:06 ` [RFC 2/2] ext4: Move ext4_fiemap to " Ritesh Harjani
2019-10-16 8:46 ` Jan Kara
2019-10-16 12:58 ` Ritesh Harjani
2019-08-27 3:58 ` [RFC 0/2] ext4: bmap & fiemap conversion to use iomap Ritesh Harjani
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=20190820130634.25954-1-riteshh@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbobrowski@mbobrowski.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;
as well as URLs for NNTP newsgroup(s).