From: Vivek Goyal <vgoyal@redhat.com>
To: Eryu Guan <eguan@linux.alibaba.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Amir Goldstein <amir73il@gmail.com>,
Max Reitz <mreitz@redhat.com>,
virtio-fs-list <virtio-fs@redhat.com>,
gerry@linux.alibaba.com, bergwolf@hyper.sh
Subject: Re: [Virtio-fs] [fuse-devel] 'FORGET' ordering semantics (vs unlink & NFS)
Date: Fri, 8 Jan 2021 10:26:46 -0500 [thread overview]
Message-ID: <20210108152646.GC46319@redhat.com> (raw)
In-Reply-To: <20210108041252.GT80581@e18g06458.et15sqa>
On Fri, Jan 08, 2021 at 12:12:52PM +0800, Eryu Guan wrote:
[..]
> > Anyone has other thoughts about how to reduce fragmentation in
> > implementations?
>
> There's an fuse-backend-rs[1] project hosted on cloud-hypervisor, it is
> a library to communicate with the Linux FUSE clients, which includes:
>
> - ABI layer, which defines all data structures shared between linux Fuse
> framework and Fuse daemons.
> - API layer, defines the interfaces for Fuse daemons to implement a
> userspace file system.
> - Transport layer, which supports both the Linux Fuse device and
> virtio-fs protocol.
> - VFS/pseudo_fs, an abstraction layer to support multiple file systems
> by a single virtio-fs device.
> - A sample passthrough file system implementation, which passes through
> files from daemons to clients.
>
So at a high level, is this equivalent of libfuse written in rust?
Vivek
> I'm wondering if fuse-backend-rs is a proper project to work on, and
> maybe virtiofsd-rs could be switched to use it as well in the future.
>
> Thanks,
> Eryu
>
> [1] https://github.com/cloud-hypervisor/fuse-backend-rs
>
next prev parent reply other threads:[~2021-01-08 15:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 16:00 [Virtio-fs] 'FORGET' ordering semantics (vs unlink & NFS) Dr. David Alan Gilbert
2021-01-04 18:45 ` Vivek Goyal
2021-01-04 18:56 ` Dr. David Alan Gilbert
2021-01-04 19:04 ` Vivek Goyal
2021-01-04 19:16 ` Vivek Goyal
2021-01-05 11:24 ` [Virtio-fs] [fuse-devel] " Miklos Szeredi
2021-01-05 15:42 ` Vivek Goyal
2021-01-06 4:29 ` Amir Goldstein
2021-01-06 8:01 ` Miklos Szeredi
2021-01-06 9:16 ` Amir Goldstein
2021-01-06 9:27 ` Amir Goldstein
2021-01-06 13:40 ` Miklos Szeredi
2021-01-06 16:57 ` Vivek Goyal
2021-01-07 8:44 ` Miklos Szeredi
2021-01-07 10:42 ` Amir Goldstein
2021-01-07 20:10 ` Dr. David Alan Gilbert
2021-01-08 4:12 ` Eryu Guan
2021-01-08 9:08 ` Amir Goldstein
2021-01-08 9:25 ` Liu, Jiang
2021-01-08 10:18 ` Eryu Guan
2021-01-08 15:26 ` Vivek Goyal [this message]
2021-01-15 10:20 ` Peng Tao
2021-01-08 15:55 ` Vivek Goyal
2021-01-11 15:48 ` Dr. David Alan Gilbert
2021-01-05 10:11 ` Nikolaus Rath
2021-01-05 12:28 ` Dr. David Alan Gilbert
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=20210108152646.GC46319@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=bergwolf@hyper.sh \
--cc=eguan@linux.alibaba.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gerry@linux.alibaba.com \
--cc=miklos@szeredi.hu \
--cc=mreitz@redhat.com \
--cc=virtio-fs@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.