From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id E6F7C677B for ; Fri, 31 Oct 2014 22:56:40 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 31 Oct 2014 15:05:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="409380948" Received: from pgsmsx103.gar.corp.intel.com ([10.221.44.82]) by FMSMGA003.fm.intel.com with ESMTP; 31 Oct 2014 14:57:13 -0700 Received: from pgsmsx107.gar.corp.intel.com (10.221.44.105) by PGSMSX103.gar.corp.intel.com (10.221.44.82) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 1 Nov 2014 06:05:26 +0800 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by PGSMSX107.gar.corp.intel.com (10.221.44.105) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 1 Nov 2014 06:05:25 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.202]) by shsmsx102.ccr.corp.intel.com ([169.254.2.156]) with mapi id 14.03.0195.001; Sat, 1 Nov 2014 06:05:25 +0800 From: "Xie, Huawei" To: Tetsuya Mukawa , "O'driscoll, Tim" Thread-Topic: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015 Thread-Index: Ac/tRv4Y4Vfrsm7FTDyvOFKZotGjVAA5dOIAAcoKvmA= Date: Fri, 31 Oct 2014 22:05:24 +0000 Message-ID: References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> <54487348.60805@igel.co.jp> In-Reply-To: <54487348.60805@igel.co.jp> 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 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 21:56:41 -0000 Hi Tetsuya: I am implementing vhost-user, and the functionality works now. During this work, I have refactored vhost code a bit for better modularizat= ion, basically virtio part, control message part(vhost-user, vhost cuse) and data part. :)= . Let us see your patch, if its modularization is further, I will generate th= e vhost-user patch based on yours rather than mine, :). > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tetsuya Mukawa > Sent: Wednesday, October 22, 2014 8:17 PM > To: O'driscoll, Tim > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015 >=20 > Hi All, >=20 > (2014/10/22 22:48), O'driscoll, Tim wrote: > > Single Virtio Driver: Merge existing Virtio drivers into a single imple= mentation, > 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 > based 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 > legacy cuse vhost and vhost-user from DPDK apps. > Also in my patch, virtio negotiation and initialization code and virtio > handling 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 > virtio drivers. >=20 > Thanks, > Tetsuya