From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
Miklos Szeredi <mszeredi@redhat.com>,
Sage Weil <sweil@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [virtio-dev] [PATCH v3 0/2] virtio-fs: add virtio file system device
Date: Mon, 24 Jun 2019 09:57:46 -0400 [thread overview]
Message-ID: <20190624095100-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190624122318.GB3833@stefanha-x1.localdomain>
On Mon, Jun 24, 2019 at 01:23:18PM +0100, Stefan Hajnoczi wrote:
> On Tue, Jun 18, 2019 at 09:30:54PM -0400, Michael S. Tsirkin wrote:
> > On Wed, Feb 20, 2019 at 12:46:11PM +0000, Stefan Hajnoczi wrote:
> > > v3:
> > > * Remove notifications virtqueue, it's unimplemented and can be added when
> > > needed [Miklos]
> > > * Add Security Considerations and Live Migration Considerations sections
> > > [Michael]
> > > v2:
> > > * Clean up core virtio file system device spec
> > > * Add DAX window
> > >
> > > These patches add the virtio file system device, which is based on Linux FUSE
> > > but includes the DAX window extension. Similar to virtio-scsi, which
> > > transports SCSI commands, virtio-fs transports FUSE requests and the protocol
> > > documentation is not duplicated here.
> >
> > I think I prefer virtio-fuse as a name. Let's be a bit more
> > specific: we might want to add more filesystem devices later on.
>
> virtio-fs is not FUSE. Existing FUSE file system daemons cannot be
> used.
Right.
> It would be confusing to call it FUSE. The wire protocol is indeed
> based on FUSE but from a user perspective it's a completely different
> system.
I agree.
> The virtio-fs device extends the FUSE protocol with the
> virtualization-specific DAX window (and the in-development shared
> metadata versioning data structures that will be added to a future
> spec).
>
> Finally, users are likely to be confused and associate virtio-fuse with
> outdated FUSE issues that have long since been solved. virtio-fs
> performs really well and that's not something that people associate with
> FUSE :-).
>
> For these reasons I think we should continue to call it virtio-fs.
>
> Stefan
I just wish we came up with something more specific than
"a filesystem". Any ideas?
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2019-06-24 13:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 12:46 [virtio-dev] [PATCH v3 0/2] virtio-fs: add virtio file system device Stefan Hajnoczi
2019-02-20 12:46 ` [virtio-dev] [PATCH v3 1/2] content: " Stefan Hajnoczi
2019-02-22 14:31 ` Dr. David Alan Gilbert
2019-02-25 15:54 ` Stefan Hajnoczi
2019-02-25 16:11 ` [virtio-dev] " Dr. David Alan Gilbert
2019-02-27 16:19 ` Stefan Hajnoczi
2019-06-19 1:29 ` [virtio-dev] " Michael S. Tsirkin
2019-07-23 15:58 ` Stefan Hajnoczi
2019-02-20 12:46 ` [virtio-dev] [PATCH v3 2/2] virtio-fs: add DAX window Stefan Hajnoczi
2019-06-19 1:41 ` Michael S. Tsirkin
2019-06-24 13:58 ` Stefan Hajnoczi
2019-06-24 14:10 ` Michael S. Tsirkin
2019-06-25 9:55 ` Dr. David Alan Gilbert
2019-06-27 14:09 ` Michael S. Tsirkin
2019-07-17 10:48 ` Stefan Hajnoczi
[not found] ` <20190717124258.GA13761@redhat.com>
2019-07-23 13:32 ` Stefan Hajnoczi
[not found] ` <20190723140855.GA11628@redhat.com>
2019-07-23 14:52 ` Stefan Hajnoczi
[not found] ` <20190723155623.GA19189@redhat.com>
2019-07-24 8:33 ` Stefan Hajnoczi
2019-06-19 1:30 ` [virtio-dev] [PATCH v3 0/2] virtio-fs: add virtio file system device Michael S. Tsirkin
2019-06-24 12:23 ` Stefan Hajnoczi
2019-06-24 13:57 ` Michael S. Tsirkin [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=20190624095100-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mszeredi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=sweil@redhat.com \
--cc=swhiteho@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-dev@lists.oasis-open.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 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.