From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tim.o'driscoll@intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 2FCC97E99
 for <dev@dpdk.org>; Thu, 23 Oct 2014 13:20:20 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by fmsmga101.fm.intel.com with ESMTP; 23 Oct 2014 04:28:43 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="404762750"
Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159])
 by FMSMGA003.fm.intel.com with ESMTP; 23 Oct 2014 04:21:00 -0700
Received: from irsmsx102.ger.corp.intel.com ([169.254.2.25]) by
 IRSMSX104.ger.corp.intel.com ([169.254.5.58]) with mapi id 14.03.0195.001;
 Thu, 23 Oct 2014 12:27:42 +0100
From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>
Thread-Topic: [dpdk-announce] DPDK Features for Q1 2015
Thread-Index: Ac/tRv4Y4Vfrsm7FTDyvOFKZotGjVABIH/kAABKraZA=
Date: Thu, 23 Oct 2014 11:27:41 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C40096@IRSMSX102.ger.corp.intel.com>
References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com>
 <54487348.60805@igel.co.jp>
In-Reply-To: <54487348.60805@igel.co.jp>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
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: Thu, 23 Oct 2014 11:20:23 -0000

> From: Tetsuya Mukawa [mailto:mukawa@igel.co.jp]
>=20
> (2014/10/22 22:48), O'driscoll, Tim wrote:
> > Single Virtio Driver: Merge existing Virtio drivers into a single
> implementation, incorporating the best features from each of the existing
> drivers.
>=20
> It's nice plan. We should do it.
> In my understanding, the following drivers could be merged into a single
> virtio PMD since they consist of similar code for handling the virtio rin=
g.
>=20
> - librte_pmd_virtio
> - librte_pmd_xenvirt
> - librte_vhost (cuse)
>=20
> librte_vhost is not a PMD, but we can easily write a librte_pmd_vhost bas=
ed
> on librte_vhost.
> Before doing it, we need to consider vhost-user extension for librte_vhos=
t.
>=20
> BTW, I have a RFC patch for librte_vhost to handle vhost-user.
> It may be the first step to merge all virtio drivers.
>=20
> My patch introduces an abstraction layer to hide differences between lega=
cy
> cuse vhost and vhost-user from DPDK apps.
> Also in my patch, virtio negotiation and initialization code and virtio h=
andling
> code is separated.
> So, legacy cuse vhost and vhost-user can share virtio handling code
>=20
> Anyway, I will send a RFC patch soon as the first step of merging all vir=
tio
> drivers.

That's great Tetsuya. There was some discussion on the mailing list previou=
sly on vhost-user in response to an RFC from Huawei Xie (http://dpdk.org/ml=
/archives/dev/2014-August/004875.html). If you're planning an additional RF=
C on this, that should help to progress things and to make sure we're not d=
uplicating work.


Tim