Christoph Hellwig 64c58d7c99 iomap: add a merge boundary flag ... File systems might have boundaries over which merges aren't possible. In fact these are very common, although most of the time some kind of header at the beginning of this region (e.g. XFS alloation groups, ext4 block groups) automatically create a merge barrier. But if that is not present, say for a device purely used for data we need to manually communicate that to iomap. Add a IOMAP_F_BOUNDARY flag to never merge I/O into a previous mapping. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Darrick J. Wong <djwong@kernel.org>		2024-11-05 13:38:39 -08:00
..
buffered-io.c	iomap: add a merge boundary flag	2024-11-05 13:38:39 -08:00
direct-io.c	iomap: remove set_memor_ro() on zero page	2024-09-03 15:01:23 +02: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	kbuild: use $(src) instead of $(srctree)/$(src) for source directory	2024-05-10 04:34:52 +09: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 processed for iomap_iter	2024-02-21 08:37:50 +01:00