From: Christoph Hellwig <hch@lst.de>
To: linux-xfs@vger.kernel.org
Cc: axboe@fb.com, kent.overstreet@gmail.com,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: an iomap-based direct I/O implementation V2
Date: Fri, 4 Nov 2016 10:21:14 -0600 [thread overview]
Message-ID: <1478276479-10749-1-git-send-email-hch@lst.de> (raw)
Hi all,
this series adds a new direct I/O implementation based on the iomap
interface, and switches XFS to use it.
The first two patches are a resend of my earlier series to remove the
XFS iolock. They are needed for the lockdep assert in the new iomap
code.
The rest implements a new iomap_dio_rw direct I/O implementation and
switches XFS to use it.
Note that this series is on top of a merge of the XFS for-next
tree with the block tree, which has a new helper needed for this
implementation. This is the block tree it's on top of:
git://git.kernel.dk/linux-block for-4.10/block
To make everyones life easier І also have a git tree with the merge
plus the patches in this series available here:
git://git.infradead.org/users/hch/vfs.git iomap-dio.2
Changes since V1:
- dropped the bio_iov_iter_get_pages patch, now merged in the block tree
- rebased on top of a merge of the XFS tree with the block tree
- stopped using WRITE_ODIRECT which has been removed in the block tree
next reply other threads:[~2016-11-04 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:21 Christoph Hellwig [this message]
2016-11-04 16:21 ` [PATCH 1/5] locking/lockdep: Provide a type check for lock_is_held Christoph Hellwig
2016-11-04 16:21 ` [PATCH 2/5] xfs: remove i_iolock and use i_rwsem in the VFS inode instead Christoph Hellwig
2016-11-04 16:21 ` [PATCH 3/5] fs: make sb_init_dio_done_wq available outside of direct-io.c Christoph Hellwig
2016-11-04 16:21 ` [PATCH 4/5] iomap: implement direct I/O Christoph Hellwig
2016-11-04 20:56 ` Jens Axboe
2016-11-05 15:10 ` Kent Overstreet
2016-11-05 18:14 ` Avi Kivity
2016-11-06 16:36 ` Christoph Hellwig
2016-11-06 22:40 ` Dave Chinner
2016-11-07 15:08 ` Christoph Hellwig
2016-11-08 1:38 ` Dave Chinner
2016-11-04 16:21 ` [PATCH 5/5] xfs: use iomap_dio_rw Christoph Hellwig
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=1478276479-10749-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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).