linux

iv/linux

History

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

iomap: Make sure iomap_end is called after iomap_begin

2020-07-06 10:49:27 -07:00

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

fs: handle FIEMAP_FLAG_SYNC in fiemap_prep