On Fri, Jun 06, 2025 at 04:37:57PM -0700, Joanne Koong wrote: > Add a new iomap type, IOMAP_IN_MEM, that represents data that resides in > memory and does not map to or depend on the block layer and is not > embedded inline in an inode. This will be used for example by filesystems > such as FUSE where the data is in memory or needs to be fetched from a > server and is not coupled with the block layer. This lets these > filesystems use some of the internal features in iomaps such as > granular dirty tracking for large folios. How does this differ from the naming of the existing flags? Nothing here explains why we need a new type vs reusing the existing ones.
