From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tetsuya Mukawa Subject: Re: [dpdk-announce] DPDK Features for Q1 2015 Date: Thu, 23 Oct 2014 12:17:28 +0900 Message-ID: <54487348.60805@igel.co.jp> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "O'driscoll, Tim" Return-path: In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi All, (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 driv= ers. 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. - librte_pmd_virtio - librte_pmd_xenvirt - librte_vhost (cuse) 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. BTW, I have a RFC patch for librte_vhost to handle vhost-user. It may be the first step to merge all virtio drivers. 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 Anyway, I will send a RFC patch soon as the first step of merging all virtio drivers. Thanks, Tetsuya