qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: berrange@redhat.com, slp@redhat.com, qemu-devel@nongnu.org,
	virtio-fs@redhat.com, stefanha@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH v2] Deprecate C virtiofsd
Date: Thu, 10 Feb 2022 20:44:04 +0000	[thread overview]
Message-ID: <20220210204404.GA22879@redhat.com> (raw)
In-Reply-To: <20220210174714.19843-1-dgilbert@redhat.com>

On Thu, Feb 10, 2022 at 05:47:14PM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> There's a nice new Rust implementation out there; recommend people
> do new work on that.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  docs/about/deprecated.rst | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 47a594a3b6..3c73d22729 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -454,3 +454,20 @@ nanoMIPS ISA
>  
>  The ``nanoMIPS`` ISA has never been upstreamed to any compiler toolchain.
>  As it is hard to generate binaries for it, declare it deprecated.
> +
> +Tools
> +-----
> +
> +virtiofsd
> +'''''''''
> +
> +There is a new Rust implementation of ``virtiofsd`` at
> +``https://gitlab.com/virtio-fs/virtiofsd``;
> +since this is now marked stable, new development should be done on that
> +rather than the existing C version in the QEMU tree.
> +The C version will still accept fixes and patches that
> +are already in development for the moment, but will eventually
> +be deleted from this tree.
> +New deployments should use the Rust version, and existing systems
> +should consider moving to it.  The command line and feature set
> +is very close and moving should be simple.

I'm not qualified to say if the Rust impl is complete enough
to replace the C version, so I won't add a reviewed tag.

However I want to say that from the point of view of downstream
packagers of qemu -- especially Fedora -- it would be helpful if we
could direct both upstream development effort and downstream packaging
into just the one virtiofsd.  So I agree in principle with this.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v



  parent reply	other threads:[~2022-02-10 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 17:47 [PATCH v2] Deprecate C virtiofsd Dr. David Alan Gilbert (git)
2022-02-10 17:52 ` Daniel P. Berrangé
2022-02-10 20:44 ` Richard W.M. Jones [this message]
2022-02-14 11:30   ` Dr. David Alan Gilbert
2022-02-14 14:27     ` Vivek Goyal
2022-02-14 11:12 ` Stefan Hajnoczi

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=20220210204404.GA22879@redhat.com \
    --to=rjones@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=slp@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@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 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).