All of lore.kernel.org
 help / color / mirror / Atom feed
From: Horst Birthelmer <horst@birthelmer.de>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
	fuse-devel@lists.linux.dev,  linux-fsdevel@vger.kernel.org
Subject: Re: Re: [PATCH] fuse: add fusex filesystem
Date: Tue, 12 May 2026 12:29:42 +0200	[thread overview]
Message-ID: <agL_Wt6GrgUW22LB@fedora.fritz.box> (raw)
In-Reply-To: <CAJfpegvYM2bdAJJHaqydxRzyVPNwOU95-MS5F+YrnOkJR+6yNg@mail.gmail.com>

On Tue, May 12, 2026 at 10:11:16AM +0200, Miklos Szeredi wrote:
> On Thu, 7 May 2026 at 10:37, Horst Birthelmer <horst@birthelmer.de> wrote:
> 
> > Where do you see the biggest challenge for this. To me, it doesn't look impossible to add that,
> > but I'm sure I'm missing a lot in this context.
> 
> The biggest challenge I see is API design.  I'd really like to have a
> simple and consistent API for this.

OK, that is a valid goal, I guess.

I have tried to come up with a fusex 'module' that does all operations over
io-uring since it is a lot easier to just support one way of transport.

Then I have written a very primitive passthrough to test the user space
interface and I can get it to work with some small changes to the interface
mostly due to the small header space on the ring.

I have done this to check how fast I can have something workable with the 
new interface since I'm supposed to add compound commands.

Do you think it is worth pursuing further?

> 
> First task: need to document the current interface, which is long
> overdue.  Here's a start:
> 
> https://docs.google.com/document/d/1SInG6nc5dF-db3WtCqFOnRDCY1jRl5JQ0Toiryn2PRc/edit?usp=sharing
> 
> This needs refinement, i.e. try to document by cache type, how is the
> cache used, invalidated, etc.
> 
> Thanks,
> Miklos

  reply	other threads:[~2026-05-12 10:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 10:20 [PATCH] fuse: add fusex filesystem Miklos Szeredi
2026-05-07  8:31 ` Horst Birthelmer
2026-05-08 13:01   ` Amir Goldstein
2026-05-12  8:17     ` Miklos Szeredi
2026-05-12 13:08       ` Amir Goldstein
2026-05-12 13:46         ` Bernd Schubert
2026-05-12 21:07           ` Amir Goldstein
2026-05-12 21:26             ` Bernd Schubert
2026-05-12  8:11   ` Miklos Szeredi
2026-05-12 10:29     ` Horst Birthelmer [this message]
2026-05-08 17:29 ` Horst Birthelmer
2026-05-12  8:20   ` Miklos Szeredi
2026-05-11  8:50 ` Horst Birthelmer
2026-05-12  8:34   ` Miklos Szeredi
2026-05-12  5:05 ` Joanne Koong
2026-05-12  9:18   ` Miklos Szeredi
2026-05-12 13:22     ` Amir Goldstein
2026-05-12 19:22       ` Joanne Koong
2026-05-12 21:28         ` Amir Goldstein
2026-05-14 23:24           ` Joanne Koong
2026-05-15 20:17             ` Amir Goldstein
2026-05-15 22:32               ` Joanne Koong
2026-05-15 23:18                 ` Amir Goldstein
2026-05-12 17:33     ` Joanne Koong
2026-05-12 20:37       ` Darrick J. Wong
2026-05-21 17:21 ` Bernd Schubert
2026-05-26 16:15 ` Luis Henriques

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=agL_Wt6GrgUW22LB@fedora.fritz.box \
    --to=horst@birthelmer.de \
    --cc=fuse-devel@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.