All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Loftus, Ciara" <ciara.loftus@intel.com>,
	Huawei Xie <huawei.xie@intel.com>,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>,
	"Wang, Zhihong" <zhihong.wang@intel.com>,
	"Hu, Jiayu" <jiayu.hu@intel.com>,
	Tetsuya Mukawa <mukawa@igel.co.jp>
Subject: Re: [RFC] remove vhost-cuse
Date: Fri, 15 Jul 2016 16:42:08 +0800	[thread overview]
Message-ID: <20160715084208.GF5146@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20160711035955.GA18850@yliu-dev.sh.intel.com>

You see that no body cares it :)

So I will make a patch to mark vhost-cuse as deprecated shortly.
Thomas, works to you?

	--yliu

On Mon, Jul 11, 2016 at 11:59:55AM +0800, Yuanhan Liu wrote:
> It's something echoed around in my mind for a long while, and here I'm
> gonna make it public: a proposal to remove vhost-cuse.
> 
> 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.
> 
> A talk with Huawei offline showed that he backs this proposal. I was
> also told by Ciara that she actually had the same idea: she has already
> cooked a patch to remove vhost-cuse support from OVS:
> 
>     http://openvswitch.org/pipermail/dev/2016-July/074696.html
> 
> So I'm proposing to mark vhost-cuse as deprecated in this release and
> remove it completely at the next release (v16.11).
> 
> Comments/thoughts, or objections?
> 
> 	--yliu

  reply	other threads:[~2016-07-15  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11  3:59 [RFC] remove vhost-cuse Yuanhan Liu
2016-07-15  8:42 ` Yuanhan Liu [this message]
2016-07-15  9:14   ` Thomas Monjalon
2016-07-15 12:29     ` Yuanhan Liu

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=20160715084208.GF5146@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=jiayu.hu@intel.com \
    --cc=mukawa@igel.co.jp \
    --cc=thomas.monjalon@6wind.com \
    --cc=zhihong.wang@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 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.