Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: Re: [PATCHSET RFC[RAP]] fuse: allow servers to use iomap for better file IO performance
Date: Wed, 21 May 2025 17:21:01 -0700	[thread overview]
Message-ID: <20250522002101.GD9705@frogsfrogsfrogs> (raw)
In-Reply-To: <174787195502.1483178.17485675069927796174.stgit@frogsfrogsfrogs>

Whoops, my eyes are tired and my script to strip out linux-xfs and cem
from the cc lines didn't work because I inverted a space and a comma in
the regexp.

Sorry about the noise.  Can we move off patchbomb development already?

--D

On Wed, May 21, 2025 at 05:01:22PM -0700, Darrick J. Wong wrote:
> 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: fix livelock in synchronous file put from fuseblk workers
>  * iomap: exit early when iomap_iter is called with zero length
>  * fuse: implement the basic iomap mechanisms
>  * fuse: add a notification to add new iomap devices
>  * fuse: send FUSE_DESTROY to userspace when tearing down an iomap connection
>  * 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: implement large folios for iomap pagecache files
>  * fuse: use an unrestricted backing device with iomap pagecache io
>  * fuse: advertise support for iomap
> ---
>  fs/fuse/fuse_i.h          |  135 ++++
>  fs/fuse/fuse_trace.h      |  845 ++++++++++++++++++++++++++
>  include/uapi/linux/fuse.h |  138 ++++
>  fs/fuse/Kconfig           |   23 +
>  fs/fuse/Makefile          |    1 
>  fs/fuse/dev.c             |   26 +
>  fs/fuse/dir.c             |   14 
>  fs/fuse/file.c            |   85 ++-
>  fs/fuse/file_iomap.c      | 1445 +++++++++++++++++++++++++++++++++++++++++++++
>  fs/fuse/inode.c           |   23 +
>  fs/iomap/iter.c           |    5 
>  11 files changed, 2730 insertions(+), 10 deletions(-)
>  create mode 100644 fs/fuse/file_iomap.c
> 
> 

      parent reply	other threads:[~2025-05-22  0:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250521235837.GB9688@frogsfrogsfrogs>
2025-05-22  0:01 ` [PATCHSET RFC[RAP]] fuse: allow servers to use iomap for better file IO performance Darrick J. Wong
2025-05-22  0:02   ` [PATCH 01/11] fuse: fix livelock in synchronous file put from fuseblk workers Darrick J. Wong
2025-05-29 11:08     ` Miklos Szeredi
2025-05-31  1:08       ` Darrick J. Wong
2025-06-06 13:54         ` Miklos Szeredi
2025-06-09 18:13           ` Darrick J. Wong
2025-06-09 20:29             ` Darrick J. Wong
2025-05-22  0:02   ` [PATCH 02/11] iomap: exit early when iomap_iter is called with zero length Darrick J. Wong
2025-05-22  0:03   ` [PATCH 03/11] fuse: implement the basic iomap mechanisms Darrick J. Wong
2025-05-29 22:15     ` Joanne Koong
2025-05-29 23:15       ` Joanne Koong
2025-06-03  0:13         ` Darrick J. Wong
2025-05-22  0:03   ` [PATCH 04/11] fuse: add a notification to add new iomap devices Darrick J. Wong
2025-05-22 16:46     ` Amir Goldstein
2025-05-22 17:11       ` Darrick J. Wong
2025-05-22  0:03   ` [PATCH 05/11] fuse: send FUSE_DESTROY to userspace when tearing down an iomap connection Darrick J. Wong
2025-05-22  0:04   ` [PATCH 06/11] fuse: implement basic iomap reporting such as FIEMAP and SEEK_{DATA,HOLE} Darrick J. Wong
2025-05-22  0:04   ` [PATCH 07/11] fuse: implement direct IO with iomap Darrick J. Wong
2025-05-22  0:04   ` [PATCH 08/11] fuse: implement buffered " Darrick J. Wong
2025-05-22  0:04   ` [PATCH 09/11] fuse: implement large folios for iomap pagecache files Darrick J. Wong
2025-05-22  0:05   ` [PATCH 10/11] fuse: use an unrestricted backing device with iomap pagecache io Darrick J. Wong
2025-05-22  0:05   ` [PATCH 11/11] fuse: advertise support for iomap Darrick J. Wong
2025-05-22  0:21   ` Darrick J. Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250522002101.GD9705@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox