Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).

We never used vhost-cuse in any of our exampled, documentations or tests
(It seems we started "late enough").

So again I think it is a good change to drop rather unmaintained parts to
make the rest more stable:
Acked-by: Christian Ehrhardt <christian.ehrhardt at canonical.com>

Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

On Wed, Jul 27, 2016 at 8:59 PM, Jan Viktorin <viktorin at rehivetech.com>
wrote:

> On Fri, 15 Jul 2016 20:28:33 +0800
> Yuanhan Liu <yuanhan.liu at linux.intel.com> wrote:
>
> > 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 at linux.intel.com>
> > Acked-by: Ciara Loftus <ciara.loftus at intel.com>
> > Acked-by: Thomas Monjalon <thomas.monjalon at 6wind.com>
> > Acked-by: Rich Lane <rich.lane at bigswitch.com>
>
> Acked-by: Jan Viktorin <viktorin at rehivetech.com>
>

Reply via email to