From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <huawei.xie@intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 78D8538EB
 for <dev@dpdk.org>; Tue, 16 Sep 2014 03:32:59 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by fmsmga101.fm.intel.com with ESMTP; 15 Sep 2014 18:38:18 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="386559742"
Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206])
 by FMSMGA003.fm.intel.com with ESMTP; 15 Sep 2014 18:31:13 -0700
Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by
 FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS)
 id 14.3.195.1; Mon, 15 Sep 2014 18:36:37 -0700
Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by
 FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS)
 id 14.3.195.1; Mon, 15 Sep 2014 18:36:37 -0700
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.203]) by
 SHSMSX103.ccr.corp.intel.com ([169.254.4.204]) with mapi id 14.03.0195.001;
 Tue, 16 Sep 2014 09:36:29 +0800
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Linhaifeng <haifeng.lin@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support
 into DPDK vhost library
Thread-Index: Ac/BHV0IrPGOjNirTxKCPui4m3t8YwAAB/VwA2y7OQAAn3yg4A==
Date: Tue, 16 Sep 2014 01:36:29 +0000
Message-ID: <C37D651A908B024F974696C65296B57B0F29E6FE@SHSMSX101.ccr.corp.intel.com>
References: <C37D651A908B024F974696C65296B57B0F27BC38@SHSMSX101.ccr.corp.intel.com>
 <5413D5DA.9030607@huawei.com>
In-Reply-To: <5413D5DA.9030607@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 01:33:01 -0000

Hi Haifeng:
Might be in the release after 1.8.

> -----Original Message-----
> From: Linhaifeng [mailto:haifeng.lin@huawei.com]
> Sent: Saturday, September 13, 2014 1:28 PM
> To: Xie, Huawei; dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support
> into DPDK vhost library
>=20
> when will publish ?
>=20
> On 2014/8/26 19:05, Xie, Huawei wrote:
> > Hi all:
> > We are implementing qemu official vhost-user interface into DPDK vhost
> library, 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 =
available
> after qemu 2.1
> >
> > BR.
> > huawei
> >
> >