Re: an iomap-based direct I/O implementation V3

[Dave Chinner <david@fromorbit.com>]

On Sun, Nov 13, 2016 at 08:07:29PM +0100, Christoph Hellwig wrote:
> 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

This tree fails compilation for me.

block/blk-flush.c: In function "flush_data_end_io":
block/blk-flush.c:369:20: error: "REQ_STARTED" undeclared (first use in this function)
  rq->cmd_flags &= ~REQ_STARTED;
                    ^~~~~~~~~~~
block/blk-flush.c:369:20: note: each undeclared identifier is reported only once for each function it appears in

Should be RQF_STARTED, right?


> To make everyones life easie I 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.3

Is there a stable topic branch with all the relevant block changes
in it? I'd like to pull this into the XFS tree so I can test it, but
these things need to be pulled from the block tree:

	- REQ_IDLE is undefined
	- bio_iov_iter_get_pages() is undefined
	- blk_mq_poll() is undefined

Having these in a stable topic branch (or set of branches) would
make this much easier for me....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com