From: GongJinrong <jinronggong@hotmail.com>
To: "'Matthew Hall'" <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Could virtio-net-pmd co-exist with virtio-net.ko?
Date: Thu, 6 Nov 2014 17:58:21 +0800 [thread overview]
Message-ID: <COL402-EAS970D81B05332E94C7EC353B7840@phx.gbl> (raw)
In-Reply-To: <20141106082100.GA16643@mhcomputing.net>
Hi, Matthew, Thanks a lot, I will try it.
-----Original Message-----
From: Matthew Hall [mailto:mhall@mhcomputing.net]
Sent: Thursday, November 06, 2014 4:21 PM
To: GongJinrong
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Could virtio-net-pmd co-exist with virtio-net.ko?
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.
prev parent reply other threads:[~2014-11-06 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 2:24 GongJinrong
2014-11-06 8:21 ` Matthew Hall
2014-11-06 9:58 ` GongJinrong [this message]
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=COL402-EAS970D81B05332E94C7EC353B7840@phx.gbl \
--to=jinronggong@hotmail.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).