From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 6E6767E80 for ; Wed, 22 Oct 2014 21:14:56 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id C9ED780C50B; Wed, 22 Oct 2014 12:22:19 -0700 (PDT) Date: Wed, 22 Oct 2014 12:22:19 -0700 From: Matthew Hall To: "O'driscoll, Tim" Message-ID: <20141022192219.GB10424@mhcomputing.net> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Wed, 22 Oct 2014 19:14:56 -0000 On Wed, Oct 22, 2014 at 01:48:36PM +0000, 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. Tim, There is a lot of good stuff in there. Specifically, in the virtio-net case above, I have discovered, and Sergio at Intel just reproduced today, that neither virtio PMD works at all inside of VirtualBox. One can't init, and the other gets into an infinite loop. But yet it's claiming support for VBox on the DPDK Supported NICs page though it doesn't seem it ever could have worked. So I'd like to request an initiative alongside any virtio-net and/or vmxnet3 type of changes, to make some kind of a Virtualization Test Lab, where we support VMWare ESXi, QEMU, Xen, VBox, and the other popular VM systems. Otherwise it's hard for us community / app developers to make the DPDK available to end users in simple, elegant ways, such as packaging it into Vagrant VM's, Amazon AMI's etc. which are prebaked and ready-to-run. Note personally of course I prefer using things like the 82599... but these are only going to be present after the customers have begun to adopt and test in the virtual environment, then they decide they like it and want to scale up to bigger boxes. Another thing which would help in this area would be additional improvements to the NUMA / socket / core / number of NICs / number of queues autodetections. To write a single app which can run on a virtual card, a hardware card without RSS available, and a hardware card with RSS available, in a thread-safe, flow-safe way, is somewhat complex at the present time. I'm running into this in the VM based environments because most VNIC's don't have RSS and it complicates the process of keeping consistent state of the flows among the cores. Thanks, Matthew.