From patchwork Fri Jul 15 12:28:33 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yuanhan Liu X-Patchwork-Id: 14851 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 7AB295581; Fri, 15 Jul 2016 14:25:36 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 5881A532D for ; Fri, 15 Jul 2016 14:25:34 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 15 Jul 2016 05:25:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos; i="5.28,368,1464678000"; d="scan'208"; a="1022334524" Received: from yliu-dev.sh.intel.com ([10.239.67.162]) by fmsmga002.fm.intel.com with ESMTP; 15 Jul 2016 05:25:26 -0700 From: Yuanhan Liu To: dev@dpdk.org Cc: Thomas Monjalon , Yuanhan Liu Date: Fri, 15 Jul 2016 20:28:33 +0800 Message-Id: <1468585713-28557-1-git-send-email-yuanhan.liu@linux.intel.com> X-Mailer: git-send-email 1.9.0 Subject: [dpdk-dev] [PATCH] doc: deprecate vhost-cuse X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 Acked-by: Ciara Loftus Acked-by: Thomas Monjalon Acked-by: Rich Lane Acked-by: Jan Viktorin Acked-by: Christian Ehrhardt --- doc/guides/rel_notes/deprecation.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index f502f86..ee99558 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -41,3 +41,7 @@ Deprecation Notices * The mempool functions for single/multi producer/consumer are deprecated and will be removed in 16.11. It is replaced by rte_mempool_generic_get/put functions. + +* The vhost-cuse will be removed in 16.11. Since v2.1, a large majority of + development effort has gone to vhost-user, such as multiple-queue, live + migration, reconnect etc. Therefore, vhost-user should be used instead.