From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz, tytso@mit.edu,
riteshh@linux.ibm.com
Subject: [PATCH 0/5] ext4: direct IO via iomap infrastructure
Date: Mon, 12 Aug 2019 22:52:19 +1000 [thread overview]
Message-ID: <cover.1565609891.git.mbobrowski@mbobrowski.org> (raw)
This patch series converts the ext4 direct IO code paths to make use of the
iomap infrastructure and removes the old buffer_head direct-io based
implementation. The result is that ext4 is converted to the newer framework
and that it may _possibly_ gain a performance boost for O_SYNC | O_DIRECT IO.
These changes have been tested using xfstests in both DAX and non-DAX modes
using various configurations i.e. 4k, dioread_nolock, dax.
Matthew Bobrowski (5):
ext4: introduce direct IO read code path using iomap infrastructure
ext4: move inode extension/truncate code out from ext4_iomap_end()
iomap: modify ->end_io() calling convention
ext4: introduce direct IO write code path using iomap infrastructure
ext4: clean up redundant buffer_head direct IO code
fs/ext4/ext4.h | 3 -
fs/ext4/extents.c | 8 +-
fs/ext4/file.c | 329 +++++++++++++++++++++++++++-------
fs/ext4/inode.c | 488 +++++---------------------------------------------
fs/iomap/direct-io.c | 9 +-
fs/xfs/xfs_file.c | 17 +-
include/linux/iomap.h | 4 +-
7 files changed, 322 insertions(+), 536 deletions(-)
--
2.16.4
--
Matthew Bobrowski
next reply other threads:[~2019-08-12 12:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 12:52 Matthew Bobrowski [this message]
2019-08-12 12:52 ` [PATCH 1/5] ext4: introduce direct IO read code path using iomap infrastructure Matthew Bobrowski
2019-08-12 17:18 ` Christoph Hellwig
2019-08-12 20:17 ` Matthew Wilcox
2019-08-13 10:45 ` Matthew Bobrowski
2019-08-12 12:52 ` [PATCH 2/5] ext4: move inode extension/truncate code out from ext4_iomap_end() Matthew Bobrowski
2019-08-12 17:18 ` Christoph Hellwig
2019-08-13 10:46 ` Matthew Bobrowski
2019-08-28 19:59 ` Jan Kara
2019-08-28 21:54 ` Matthew Bobrowski
2019-08-29 8:18 ` Jan Kara
2019-08-12 12:53 ` [PATCH 3/5] iomap: modify ->end_io() calling convention Matthew Bobrowski
2019-08-12 17:18 ` Christoph Hellwig
2019-08-13 10:43 ` Matthew Bobrowski
2019-08-12 12:53 ` [PATCH 4/5] ext4: introduce direct IO write code path using iomap infrastructure Matthew Bobrowski
2019-08-12 17:04 ` RITESH HARJANI
2019-08-13 12:58 ` Matthew Bobrowski
2019-08-13 14:35 ` Darrick J. Wong
2019-08-14 9:51 ` Matthew Bobrowski
2019-08-12 17:34 ` Christoph Hellwig
2019-08-13 10:45 ` Matthew Bobrowski
2019-08-28 20:26 ` Jan Kara
2019-08-28 22:32 ` Dave Chinner
2019-08-29 8:03 ` Jan Kara
2019-08-29 11:47 ` Matthew Bobrowski
2019-08-29 11:45 ` Matthew Bobrowski
2019-08-29 12:38 ` Jan Kara
2019-08-12 12:53 ` [PATCH 5/5] ext4: clean up redundant buffer_head direct IO code Matthew Bobrowski
2019-08-12 17:31 ` [PATCH 0/5] ext4: direct IO via iomap infrastructure RITESH HARJANI
2019-08-13 11:10 ` Matthew Bobrowski
2019-08-13 12:27 ` RITESH HARJANI
2019-08-14 9:48 ` Matthew Bobrowski
2019-08-14 11:58 ` RITESH HARJANI
2019-08-21 13:14 ` Matthew Bobrowski
2019-08-22 12:00 ` Matthew Bobrowski
2019-08-22 14:11 ` Ritesh Harjani
2019-08-24 3:18 ` Matthew Bobrowski
2019-08-24 3:55 ` Darrick J. Wong
2019-08-24 23:04 ` Christoph Hellwig
2019-08-27 9:52 ` Matthew Bobrowski
2019-08-28 12:05 ` Matthew Bobrowski
2019-08-28 14:27 ` Theodore Y. Ts'o
2019-08-28 18:02 ` Jan Kara
2019-08-29 6:36 ` Christoph Hellwig
2019-08-29 11:20 ` Matthew Bobrowski
2019-08-29 14:41 ` Christoph Hellwig
2019-08-23 13:43 ` [RFC 1/1] ext4: PoC implementation of option-1 Ritesh Harjani
2019-08-23 13:49 ` 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=cover.1565609891.git.mbobrowski@mbobrowski.org \
--to=mbobrowski@mbobrowski.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.