From: Surya Nimmagadda <nscsekhar@juniper.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Very low performance with l2fwd in a VM with PCI Passthrough
Date: Fri, 7 Mar 2014 03:08:09 +0000 [thread overview]
Message-ID: <059A249A-F4A5-48BD-A5F0-7C0DA2CAFD2A@juniper.net> (raw)
Hi,
I am seeing very low throughput when I run l2fwd in a VM.
When I send 1g data, I could see only about 10mbps of traffic being received by the VM.
I dont see this problem when running l2fwd on the host. I could get 10gbps traffic in and out of both the ports.
My setup details are
- Traffic coming in on a 10G interface(eth0) and going out on another 10G interface(eth1)
- Both 10G NICs are 82599
- Created virtual functions eth5 and eth8 on eth0 and eth1 respectively
- eth5 and eth8 are mapped to eth0 and eth1 in a VM, with device type as e1000 in Passthru mode.
- Host OS : Centos 6.2, Guest OS : Ubuntu 12.04
<…>
Network devices using IGB_UIO driver
====================================
0000:00:07.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
0000:00:08.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
<…>
The counters on the virtual interface (eth5/eth8) show all 10g traffic received, but I see very 10mbps worth traffic at the l2fwd app counters on the VM.
I also see the following logs in the VM dmesg output.
[75399.491215] irq 0xb not handled
[75400.142025] irq 0xb not handled
[75400.142150] irq 0xb not handled
[75400.142913] irq 0xb not handled
[75400.142920] irq 0xb not handled
Has anyone seen this issue? Am I missing anything?
Thanks,
Surya
next reply other threads:[~2014-03-07 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 3:08 Surya Nimmagadda [this message]
2014-03-07 6:00 ` Surya Nimmagadda
2014-03-07 9:27 ` Richardson, Bruce
2014-03-09 8:30 ` Surya Nimmagadda
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=059A249A-F4A5-48BD-A5F0-7C0DA2CAFD2A@juniper.net \
--to=nscsekhar@juniper.net \
--cc=dev@dpdk.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 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).