From: Matthew Hall <mhall-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
To: GongJinrong <jinronggong-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Could virtio-net-pmd co-exist with virtio-net.ko?
Date: Thu, 6 Nov 2014 00:21:00 -0800 [thread overview]
Message-ID: <20141106082100.GA16643@mhcomputing.net> (raw)
In-Reply-To: <COL402-EAS12758C78530A6380F94E412B7840-MsuGFMq8XAE@public.gmane.org>
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.
next prev parent reply other threads:[~2014-11-06 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 2:24 Could virtio-net-pmd co-exist with virtio-net.ko? GongJinrong
[not found] ` <COL402-EAS12758C78530A6380F94E412B7840-MsuGFMq8XAE@public.gmane.org>
2014-11-06 8:21 ` Matthew Hall [this message]
[not found] ` <20141106082100.GA16643-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2014-11-06 9:58 ` GongJinrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141106082100.GA16643@mhcomputing.net \
--to=mhall-hv3ognyu3jfzzajbqzqcxq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=jinronggong-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.