From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wiles, Keith" Subject: Re: [PATCH v2 00/24] Single virtio implementation Date: Tue, 27 Jan 2015 03:42:00 +0000 Message-ID: References: <1421298930-15210-1-git-send-email-changchun.ouyang@intel.com> <1422326164-13697-1-git-send-email-changchun.ouyang@intel.com> <20150127030612.GA13138@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Matthew Hall , "Ouyang, Changchun" Return-path: In-Reply-To: <20150127030612.GA13138-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> Content-Language: en-US Content-ID: 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" On 1/26/15, 8:06 PM, "Matthew Hall" wrote: >On Tue, Jan 27, 2015 at 10:35:40AM +0800, Ouyang Changchun wrote: >> This is the patch set for single virtio implementation. >> =20 >> Why we need single virtio? >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >> As we know currently there are at least 3 virtio PMD driver >>implementations: >> A) lib/librte_pmd_virtio(refer as virtio A); >> B) virtio_net_pmd by 6wind(refer as virtio B); >> C) virtio by Brocade/vyatta(refer as virtio C); >> =20 >> Integrating 3 implementations into one could reduce the maintaining >>cost and time, >> in other hand, user don't need practice their application on 3 variant >>one by one to see >> which one is the best for them; > >Thank you so much for this, using virtio drivers in DPDK has been messy >and=20 >unpleasant in the past, and you clearly wrote a lot of nice new code to >help=20 >improve it all. > >Previously I'd reported a bug, where all RTE virtio drivers I tried (A >and B,=20 >because I did not know C existed), failed to work with the virtio-net >interfaces exposed in VirtualBox, due to various strange errors, and they >all=20 >only worked with the virtio-net interfaces from qemu. > >I wanted to find out if we managed to fix this other problem, because I >would=20 >really like to use the Vagrant VM deployment tool >(https://www.vagrantup.com/) >to distribute my open-source DPDK based application to everyone in the >open source community. > >The better the out-of-box experience of practical community-created >DPDK-based=20 >real-life example applications similar to mine, the more adoption of DPDK >and=20 >better DPDK community we will be able to have as time marches forward. > >If we could manage to get it to work in VirtualBox, then I could surely >help=20 >do some app-level testing on the new code, if we could see it in a test >branch=20 >or test repo somewhere I could access it. There is an app note on how to get DPDK working in VirtualBox, it is a bit bumpy on getting it work. Here is the link:=20 http://plvision.eu/blog/deploying-intel-dpdk-in-oracle-virtualbox/ I have not tried it, but it was suggested to me it should work. It will be nice if the new driver works better :-) > >Sincerely, >Matthew Hall