From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "Loftus, Ciara" <ciara.loftus@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: deprecate vhost-cuse
Date: Wed, 27 Jul 2016 10:31:28 +0200 [thread overview]
Message-ID: <1648280.lzNIrW0CUZ@xps13> (raw)
In-Reply-To: <74F120C019F4A64C9B78E802F6AD4CC24F8ED89E@IRSMSX106.ger.corp.intel.com>
> > Vhost-cuse was invented before vhost-user exist. The both are actually
> > doing the same thing: a vhost-net implementation in user space. But they
> > are not exactly the same thing.
> >
> > Firstly, vhost-cuse is harder for use; no one seems to care it, either.
> > Furthermore, since v2.1, a large majority of development effort has gone
> > to vhost-user. For example, we extended the vhost-user spec to add the
> > multiple queue support. We also added the vhost-user live migration at
> > v16.04 and the latest one, vhost-user reconnect that allows vhost app
> > restart without restarting the guest. Both of them are very important
> > features for product usage and none of them works for vhost-cuse.
> >
> > You now see that the difference between vhost-user and vhost-cuse is
> > big (and will be bigger and bigger as time moves forward), that you
> > should never use vhost-cuse, that we should drop it completely.
> >
> > The remove would also result to a much cleaner code base, allowing us
> > to do all kinds of extending easier.
> >
> > So here to mark vhost-cuse as deprecated in this release and will be
> > removed in the next release (v16.11).
> >
> > Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
>
> Acked-by: Ciara Loftus <ciara.loftus@intel.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
next prev parent reply other threads:[~2016-07-27 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 12:28 Yuanhan Liu
2016-07-21 11:07 ` Loftus, Ciara
2016-07-27 8:31 ` Thomas Monjalon [this message]
2016-07-27 15:57 ` Rich Lane
2016-07-27 18:59 ` [dpdk-dev] " Jan Viktorin
2016-07-28 9:10 ` Christian Ehrhardt
2016-07-28 18:12 ` Thomas Monjalon
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=1648280.lzNIrW0CUZ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).