diff options
author | Christoph Hellwig <hch@lst.de> | 2017-11-01 16:36:47 +0100 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2017-11-03 06:26:26 -0700 |
commit | a39e596baa07cb1dc19c2ead14c9fd2a30f22352 (patch) | |
tree | fa9b99af09d60b9c6f85704c6e46bd9f9905c1a2 /fs/ceph/mds_client.c | |
parent | 7b565c9f965bac269cc6a1f25c819f77044abf9d (diff) | |
download | linux-stable-a39e596baa07cb1dc19c2ead14c9fd2a30f22352.tar.gz linux-stable-a39e596baa07cb1dc19c2ead14c9fd2a30f22352.tar.bz2 linux-stable-a39e596baa07cb1dc19c2ead14c9fd2a30f22352.zip |
xfs: support for synchronous DAX faults
Return IOMAP_F_DIRTY from xfs_file_iomap_begin() when asked to prepare
blocks for writing and the inode is pinned, and has dirty fields other
than the timestamps. In __xfs_filemap_fault() we then detect this case
and call dax_finish_sync_fault() to make sure all metadata is committed,
and to insert the page table entry.
Note that this will also dirty corresponding radix tree entry which is
what we want - fsync(2) will still provide data integrity guarantees for
applications not using userspace flushing. And applications using
userspace flushing can avoid calling fsync(2) and thus avoid the
performance overhead.
[JK: Added VM_SYNC flag handling]
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'fs/ceph/mds_client.c')
0 files changed, 0 insertions, 0 deletions