xfs: don't start out with the exclusive ilock for direct I/O
authorChristoph Hellwig <hch@lst.de>
Thu, 1 Mar 2018 22:12:12 +0000 (14:12 -0800)
committerDarrick J. Wong <darrick.wong@oracle.com>
Thu, 1 Mar 2018 22:12:12 +0000 (14:12 -0800)
commitaf5b5afe9ac68406892fa343fafba4ea988c3c69
treebfd9ffb0fa066942f78042d1b647d62c3f9f80e0
parent172ed391f6e40f799273e005405041b57c343cf7
xfs: don't start out with the exclusive ilock for direct I/O

There is no reason to take the ilock exclusively at the start of
xfs_file_iomap_begin for direct I/O, given that it will be demoted
just before calling xfs_iomap_write_direct anyway.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
fs/xfs/xfs_iomap.c