linux/fs/iomap
Jens Axboe 985b71db17 iomap: use filemap_range_needs_writeback() for O_DIRECT reads
For reads, use the better variant of checking for the need to call
filemap_write_and_wait_range() when doing O_DIRECT.  This avoids falling
back to the slow path for IOCB_NOWAIT, if there are no pages to wait for
(or write out).

Link: https://lkml.kernel.org/r/20210224164455.1096727-4-axboe@kernel.dk
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Reviewed-by: Jan Kara <jack@suse.cz>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-04-30 11:20:36 -07:00
..
apply.c
buffered-io.c treewide: Change list_sort to use const pointers 2021-04-08 16:04:22 -07:00
direct-io.c iomap: use filemap_range_needs_writeback() for O_DIRECT reads 2021-04-30 11:20:36 -07:00
fiemap.c
Makefile
seek.c iomap: use mapping_seek_hole_data 2021-02-26 09:40:59 -08:00
swapfile.c iomap: improve the warnings from iomap_swapfile_activate 2021-03-26 10:55:40 -07:00
trace.c
trace.h iomap: fall back to buffered writes for invalidation failures 2020-08-05 09:24:16 -07:00