From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id E2C7938EB for ; Tue, 26 Aug 2014 13:02:12 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 26 Aug 2014 04:06:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208,217";a="377077134" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by FMSMGA003.fm.intel.com with ESMTP; 26 Aug 2014 04:01:51 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 26 Aug 2014 04:05:59 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 26 Aug 2014 04:05:59 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.198]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.219]) with mapi id 14.03.0195.001; Tue, 26 Aug 2014 19:05:57 +0800 From: "Xie, Huawei" To: "dev@dpdk.org" Thread-Topic: [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library Thread-Index: Ac/BHV0IrPGOjNirTxKCPui4m3t8YwAAB/Vw Date: Tue, 26 Aug 2014 11:05:56 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library 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: , X-List-Received-Date: Tue, 26 Aug 2014 11:02:13 -0000 Hi all: We are implementing qemu official vhost-user interface into DPDK vhost libr= ary, so there would be two coexisting implementations for user space vhost = backend. Pro and cons in my mind: Existing solution: Pros: works with qemu version before 2.1; Cons: depends on eventfd proxy = kernel module and extra maintenance effort Qemu vhost-user: Pros: qemu official us-vhost interface; Cons: only avai= lable after qemu 2.1 BR. huawei