dax: provide an iomap based dax read/write path

Browse source

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>

...

This commit is contained in:

Christoph Hellwig 2016-09-19 11:24:49 +10:00 • committed by Dave Chinner

parent b0d5e82fcf

commit a254e56812

2 changed files with 118 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

114

fs/dax.c

View file

4

include/linux/dax.h

View file