ext4: fix ext4_dax_read/write inode locking sequence for IOCB_NOWAIT
authorRitesh Harjani <riteshh@linux.ibm.com>
Thu, 12 Dec 2019 05:55:55 +0000 (11:25 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 28 Feb 2020 15:35:55 +0000 (16:35 +0100)
commit52f192660a4d1529458d72178f50cf431743b961
treefa68c6f5d6edbf355cb764ae460879d59edbaedc
parentbb36a883e32b7d3804441822e6e0d4cb3a47a19b
ext4: fix ext4_dax_read/write inode locking sequence for IOCB_NOWAIT

[ Upstream commit f629afe3369e9885fd6e9cc7a4f514b6a65cf9e9 ]

Apparently our current rwsem code doesn't like doing the trylock, then
lock for real scheme.  So change our dax read/write methods to just do the
trylock for the RWF_NOWAIT case.
This seems to fix AIM7 regression in some scalable filesystems upto ~25%
in some cases. Claimed in commit 942491c9e6d6 ("xfs: fix AIM7 regression")

Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Matthew Bobrowski <mbobrowski@mbobrowski.org>
Tested-by: Joseph Qi <joseph.qi@linux.alibaba.com>
Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
Link: https://lore.kernel.org/r/20191212055557.11151-2-riteshh@linux.ibm.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/ext4/file.c