dax: provide an iomap based dax read/write path
authorChristoph Hellwig <hch@lst.de>
Mon, 19 Sep 2016 01:24:49 +0000 (11:24 +1000)
committerDave Chinner <david@fromorbit.com>
Mon, 19 Sep 2016 01:24:49 +0000 (11:24 +1000)
commita254e568128804fc2f18490af617197a1d36675e
tree1ac13b348313bc0b9407c19a13b7945b15a56c34
parentb0d5e82fcf8249b5aca52d235c1cfabd68b253e8
dax: provide an iomap based dax read/write path

This is a much simpler implementation of the DAX read/write path
that makes use of the iomap infrastructure.  It does not try to
mirror the direct I/O calling conventions and thus doesn't have to
deal with i_dio_count or the end_io handler, but instead leaves
locking and filesystem-specific I/O completion to the caller.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/dax.c
include/linux/dax.h