From: Amir Goldstein <amir73il@gmail.com>
To: Daniel Rosenberg <drosen@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org,
Paul Lawrence <paullawrence@google.com>,
bpf <bpf@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org,
Alessio Balsini <balsini@android.com>,
Bernd Schubert <bschubert@ddn.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] fuse passthrough solutions and status
Date: Thu, 27 Apr 2023 18:58:14 +0300 [thread overview]
Message-ID: <CAOQ4uxgaPkGPppTqL0TEcrY-8h61D+1RcLbSbSnxY8XChghQaw@mail.gmail.com> (raw)
In-Reply-To: <CA+PiJmRYG=KOhjw5M+JBKHEEN1XfE2fYQhn+3NDLr_Gw3yBozA@mail.gmail.com>
On Sat, Feb 25, 2023 at 2:59 AM Daniel Rosenberg via Lsf-pc
<lsf-pc@lists.linux-foundation.org> wrote:
>
> On Fri, Feb 10, 2023 at 7:52 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > Several fuse based filesystems pass file data from an underlying
> > filesystem without modification. The added value can come from
> > changed directory structure, changed metadata or the ability to
> > intercept I/O only in special cases. This pattern is very common, so
> > optimizing it could be very worthwhile.
> >
> > I'd like to discuss proposed solutions to enabling data passthrough.
> > There are several prototypes:
> >
> > - fuse2[1] (myself, very old)
> > - fuse-passthrough[2] (Alessio Balsini, more recent)
> > - fuse-bpf[3] (Daniel Rosenberg, new)
> >
> > The scope of fuse-bpf is much wider, but it does offer conditional
> > passthrough behavior as well.
> >
> > One of the questions is how to reference underlying files. Passing
> > open file descriptors directly in the fuse messages could be
> > dangerous[4]. Setting up the mapping from an open file descriptor to
> > the kernel using an ioctl() instead should be safe.
> >
> > Other open issues:
> >
> > - what shall be the lifetime of the mapping?
> >
> > - does the mapped open file need to be visible to userspace?
> > Remember, this is a kernel module, so there's no process involved
> > where you could look at /proc/PID/fd. Adding a kernel thread for each
> > fuse instance that installs these mapped fds as actual file descriptor
> > might be the solution.
> >
> > Thanks,
> > Miklos
> >
> >
> > [1] https://lore.kernel.org/all/CAJfpegtjEoE7H8tayLaQHG9fRSBiVuaspnmPr2oQiOZXVB1+7g@mail.gmail.com/
> >
> > [2] https://lore.kernel.org/all/20210125153057.3623715-1-balsini@android.com/
> >
> > [3] https://lore.kernel.org/all/20221122021536.1629178-1-drosen@google.com/
> >
> > [4] https://lore.kernel.org/all/CAG48ez17uXtjCTa7xpa=JWz3iBbNDQTKO2hvn6PAZtfW3kXgcA@mail.gmail.com/
>
> I'd be very interested to discuss fuse-bpf, and how it aligns with the
> other efforts. I recall there being some io uring effort as well,
> though I haven't looked into that too much yet.
>
For the record, I scheduled a (30 min) session for this with you and Miklos
co-leads.
Bernd's session on FUSE uring will follow right after.
Thanks,
Amir.
prev parent reply other threads:[~2023-04-27 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 15:52 [LSF/MM/BPF TOPIC] fuse passthrough solutions and status Miklos Szeredi
2023-02-25 0:59 ` Daniel Rosenberg
2023-04-27 15:58 ` Amir Goldstein [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=CAOQ4uxgaPkGPppTqL0TEcrY-8h61D+1RcLbSbSnxY8XChghQaw@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=balsini@android.com \
--cc=bpf@vger.kernel.org \
--cc=bschubert@ddn.com \
--cc=drosen@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=paullawrence@google.com \
/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;
as well as URLs for NNTP newsgroup(s).