From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: Could virtio-net-pmd co-exist with virtio-net.ko? Date: Thu, 6 Nov 2014 00:21:00 -0800 Message-ID: <20141106082100.GA16643@mhcomputing.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev-VfR2kkLFssw@public.gmane.org To: GongJinrong Return-path: Content-Disposition: inline In-Reply-To: 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 Thu, Nov 06, 2014 at 10:24:11AM +0800, GongJinrong wrote: > Hi, Guys > > When I run virtio-net-pmd in VM, I got "virtio-net device is already > used by another driver" error message, after I removed the virtio-net.ko, it > worked, but now I cannot use the virio-net driver for another virtual NIC, > this cost that normal network performance(non-DPDK application) drops a lot, > could the virtio-net-pmd co-exist with standard virio-net driver? > > BR > John Gong I have no proof it will work perfectly, as I never got to use the virtio PMDs because neither works in VirtualBox (developer-friendly / desktop virtualization). But there is a script included in DPDK, dpdk_nic_bind.py, which should let you configure this more intelligently on a per-VNIC basis. You could try something similar to this: export RTE_SDK="${build_directory}/external/dpdk" export RTE_TOOLS="${RTE_SDK}/tools" export RTE_NIC_BIND="${RTE_TOOLS}/dpdk_nic_bind.py" "${RTE_NIC_BIND}" --status | fgrep "${PCI_ID}" "${RTE_NIC_BIND}" -b none "${PCI_ID}" "${RTE_NIC_BIND}" -b igb_uio "${PCI_ID}" "${RTE_NIC_BIND}" --status | fgrep "${PCI_ID}" Good Luck! Matthew.