Hi all, This series connects fuse (the userspace filesystem layer) to fs-iomap to get fuse servers out of the business of handling file I/O themselves. By keeping the IO path mostly within the kernel, we can dramatically improve the speed of disk-based filesystems. This enables us to move all the filesystem metadata parsing code out of the kernel and into userspace, which means that we can containerize them for security without losing a lot of performance. If you're going to start using this code, I strongly recommend pulling from my git trees, which are linked below. This has been running on the djcloud for months with no problems. Enjoy! Comments and questions are, as always, welcome. --D kernel git tree: https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=fuse-iomap --- Commits in this patchset: * fuse: implement the basic iomap mechanisms * fuse: add an ioctl to add new iomap devices * fuse: flush events and send FUSE_SYNCFS and FUSE_DESTROY on unmount * fuse: implement basic iomap reporting such as FIEMAP and SEEK_{DATA,HOLE} * fuse: implement direct IO with iomap * fuse: implement buffered IO with iomap * fuse: enable caching of timestamps * fuse: implement large folios for iomap pagecache files * fuse: use an unrestricted backing device with iomap pagecache io * fuse: advertise support for iomap * fuse: query filesystem geometry when using iomap * fuse: implement fadvise for iomap files * fuse: implement inline data file IO via iomap --- fs/fuse/fuse_i.h | 164 ++++ fs/fuse/fuse_trace.h | 1167 ++++++++++++++++++++++++++ include/uapi/linux/fuse.h | 174 ++++ fs/fuse/Kconfig | 24 + fs/fuse/Makefile | 1 fs/fuse/dev.c | 23 + fs/fuse/dir.c | 34 + fs/fuse/file.c | 138 +++ fs/fuse/file_iomap.c | 2019 +++++++++++++++++++++++++++++++++++++++++++++ fs/fuse/inode.c | 53 + 10 files changed, 3761 insertions(+), 36 deletions(-) create mode 100644 fs/fuse/file_iomap.c
