From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/9 v7] btrfs direct-io using iomap
Date: Thu, 26 Mar 2020 16:02:45 -0500 [thread overview]
Message-ID: <20200326210254.17647-1-rgoldwyn@suse.de> (raw)
This is an effort to use iomap for direct I/O in btrfs. This would
change the call from __blockdev_direct_io() to iomap_dio_rw().
The main objective is to lose the buffer head and use bio defined by
iomap code, and hopefully to use more of generic-FS codebase.
These patches are based and tested on v5.6-rc7. I have tested it against
xfstests.
The tree is available at
https://github.com/goldwynr/linux/tree/btrfs-iomap-dio
Changes since v1
- Incorporated back the efficiency change for inode locking
- Review comments about coding style and git comments
- Merge related patches into one
- Direct read to go through btrfs_direct_IO()
- Removal of no longer used function dio_end_io()
Changes since v2
- aligning iomap offset/length to the position/length of I/O
- Removed btrfs_dio_data
- Removed BTRFS_INODE_READDIO_NEED_LOCK
- Re-incorporating write efficiency changes caused lockdep_assert() in
iomap to be triggered, remove that code.
Changes since v3
- Fixed freeze on generic/095. Use iomap_end() to account for
failed/incomplete dio instead of btrfs_dio_data
Changes since v4
- moved lockdep_assert_held() to functions calling iomap_dio_rw()
This may be called immidiately after calling inode lock and
may feel not required, but it seems important.
- Removed comments which are no longer required
- Changed commit comments to make them more appropriate
Changes since v5
- restore inode_dio_wait() in truncate
- Removed lockdep_assert_held() near callers
Changes since v6
- Fixed hangs due to underlying device failures
- Removed the patch to wait while releasing pages
fs/btrfs/btrfs_inode.h | 18 --
fs/btrfs/ctree.h | 4
fs/btrfs/file.c | 124 +++++++++++++-
fs/btrfs/inode.c | 418 +++++++++++++++----------------------------------
fs/direct-io.c | 19 --
fs/iomap/direct-io.c | 17 +
include/linux/fs.h | 4
include/linux/iomap.h | 2
mm/filemap.c | 13 -
9 files changed, 274 insertions(+), 345 deletions(-)
next reply other threads:[~2020-03-26 21:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 21:02 Goldwyn Rodrigues [this message]
2020-03-26 21:02 ` [PATCH 1/9] fs: Export generic_file_buffered_read() Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 2/9] iomap: add a filesystem hook for direct I/O bio submission Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 3/9] iomap: Remove lockdep_assert_held() Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 4/9] btrfs: Switch to iomap_dio_rw() for dio Goldwyn Rodrigues
2020-03-27 8:10 ` Christoph Hellwig
2020-03-27 16:13 ` Goldwyn Rodrigues
2020-05-07 6:14 ` Christoph Hellwig
2020-05-07 11:37 ` David Sterba
2020-05-07 12:10 ` Christoph Hellwig
2020-05-07 13:44 ` Goldwyn Rodrigues
2020-05-08 3:14 ` Goldwyn Rodrigues
2020-05-09 13:59 ` Christoph Hellwig
2020-05-10 4:06 ` Goldwyn Rodrigues
2020-05-12 14:58 ` Christoph Hellwig
2020-05-12 17:19 ` Goldwyn Rodrigues
2020-05-15 14:13 ` Christoph Hellwig
2020-05-18 14:36 ` Goldwyn Rodrigues
2020-05-19 20:11 ` Goldwyn Rodrigues
2020-05-20 6:11 ` Christoph Hellwig
2020-05-22 11:36 ` David Sterba
2020-05-22 12:08 ` Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 5/9] btrfs: Use ->iomap_end() instead of btrfs_dio_data Goldwyn Rodrigues
2020-03-27 8:16 ` Christoph Hellwig
2020-03-27 16:11 ` Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 6/9] fs: Remove dio_end_io() Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 7/9] btrfs: remove BTRFS_INODE_READDIO_NEED_LOCK Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 8/9] btrfs: btrfs: split btrfs_direct_IO Goldwyn Rodrigues
2020-03-26 21:02 ` [PATCH 9/9] btrfs: unlock extents in ->iomap_end() for DIO reads Goldwyn Rodrigues
2020-03-27 15:56 ` [PATCH 0/9 v7] btrfs direct-io using iomap David Sterba
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=20200326210254.17647-1-rgoldwyn@suse.de \
--to=rgoldwyn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
/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).