Jens Axboe 3a0be38cc8 iomap: treat a write through cache the same as FUA ... Whether we have a write back cache and are using FUA or don't have a write back cache at all is the same situation. Treat them the same. This makes the IOMAP_DIO_WRITE_FUA name a bit misleading, as we have two cases that provide stable writes: 1) Volatile write cache with FUA writes 2) Normal write without a volatile write cache Rename that flag to IOMAP_DIO_STABLE_WRITE to make that clearer, and update some of the FUA comments as well. Reviewed-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>		2023-08-01 17:32:35 -06:00
..
buffered-io.c	New code for 6.5:	2023-07-02 11:14:54 -07:00
direct-io.c	iomap: treat a write through cache the same as FUA	2023-08-01 17:32:35 -06:00
fiemap.c	fs: Move many prototypes to pagemap.h	2022-03-21 12:59:02 -04:00
iter.c	iomap: write iomap validity checks	2022-11-29 09:09:17 +11:00
Makefile	iomap: build the block based code conditionally	2021-12-04 08:58:54 -08:00
seek.c	iomap: switch iomap_seek_data to use iomap_iter	2021-08-16 21:26:33 -07:00
swapfile.c	mm/swap: consider max pages in iomap_swapfile_add_extent	2021-08-18 12:47:52 -07:00
trace.c	iomap: Add DIO tracepoints	2023-04-21 08:54:47 -07:00
trace.h	iomap: Add DIO tracepoints	2023-04-21 08:54:47 -07:00