xfs: use iomap_dio_rw
authorChristoph Hellwig <hch@lst.de>
Wed, 30 Nov 2016 03:37:15 +0000 (14:37 +1100)
committerDave Chinner <david@fromorbit.com>
Wed, 30 Nov 2016 03:37:15 +0000 (14:37 +1100)
commitacdda3aae146d9b69d30e9d8a32a8d8937055523
treed72fe0a93fa456fdf5195b5ccb919648c15fd7be
parentff6a9292e6f633d596826be5ba70d3ef90cc3300
xfs: use iomap_dio_rw

Straight switch over to using iomap for direct I/O - we already have the
non-COW dio path in write_begin for DAX and files with extent size hints,
so nothing to add there.  The COW path is ported over from the old
get_blocks version and a bit of a mess, but I have some work in progress
to make it look more like the buffered I/O COW path.

This gets rid of xfs_get_blocks_direct and the last caller of
xfs_get_blocks with the create flag set, so all that code can be removed.

Last but not least I've removed a comment in xfs_filemap_fault that
refers to xfs_get_blocks entirely instead of updating it - while the
reference is correct, the whole DAX fault path looks different than
the non-DAX one, so it seems rather pointless.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Tested-by: Jens Axboe <axboe@fb.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_aops.c
fs/xfs/xfs_aops.h
fs/xfs/xfs_file.c
fs/xfs/xfs_iomap.c