xfs: use ranged writeback and invalidation for direct IO
authorDave Chinner <dchinner@redhat.com>
Tue, 2 Sep 2014 02:12:53 +0000 (12:12 +1000)
committerDave Chinner <david@fromorbit.com>
Tue, 2 Sep 2014 02:12:53 +0000 (12:12 +1000)
commit7d4ea3ce63a6bc532abb334c469c18481798af8c
treeececad5aeceda0b2ead76e6d1016a98c6b5394d5
parent834ffca6f7e345a79f6f2e2d131b0dfba8a4b67a
xfs: use ranged writeback and invalidation for direct IO

Now we are not doing silly things with dirtying buffers beyond EOF
and using invalidation correctly, we can finally reduce the ranges of
writeback and invalidation used by direct IO to match that of the IO
being issued.

Bring the writeback and invalidation ranges back to match the
generic direct IO code - this will greatly reduce the perturbation
of cached data when direct IO and buffered IO are mixed, but still
provide the same buffered vs direct IO coherency behaviour we
currently have.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_file.c