From: Anant Mudambi <amudambi@paloaltonetworks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Tx doesn't work on PCI-passthrough I350
Date: Tue, 28 Oct 2014 00:25:29 +0000 [thread overview]
Message-ID: <D074308A.123E%amudambi@paloaltonetworks.com> (raw)
Hi,
My setup:
Qemu+KVM
Host OS: CentOS, Linux kernel version 2.6.32
Guest OS: Linux kernel version 3.10.0, with a DPDK application running.
Physical NIC: Intel I350 T4 using igb driver
On guest VM: 2 (out of 4) ports of the I350 are virtualized using PCI-passthrough (no VFs, SR-IOV is not enabled in the NIC eeprom)
2 other (non-DPDK) VMs are connected through the DPDK VM as follows:
VM1---DPDK VM---VM2
On doing a ping from VM1 to VM2 (or the other way), on the DPDK VM, the packet is received on 1 port and sent out of the other but doesn't reach VM2.
I turned on CONFIG_RTE_LIBRTE_E1000_DEBUG_RX and CONFIG_RTE_LIBRTE_E1000_DEBUG_TX but couldn't figure out where the transmitted packet went.
How can I debug this issue?
For comparison, the same setup works if the guest VM uses emulated e1000 NICs. I want to use igb/PCI-passthrough to be able to use multiple RX queues.
Please let me know if any other information is required.
Thanks,
Anant
reply other threads:[~2014-10-28 0:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=D074308A.123E%amudambi@paloaltonetworks.com \
--to=amudambi@paloaltonetworks.com \
--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).