From: Jeff Weeks <jweeks@sandvine.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Intel X710 and DPDK...
Date: Tue, 10 Sep 2019 19:49:14 +0000 [thread overview]
Message-ID: <ef91c499cc7b4617a0474e80d7351b18@sandvine.com> (raw)
Hello,
I have some questions regarding the i40e driver in reference to Intel X710 NICs.
I have several 10G X710 cards on a host, mapped into a kvm-based guest via PCI-passthrough.
DPDK sees these cards (the 6 in "Other Network Devices"):
# dpdk-devbind --status
Network devices using kernel driver
===================================
0000:00:03.0 '82540EM Gigabit Ethernet Controller 100e' if=eth0 drv=e1000 unused=uio_pci_generic
0000:00:04.0 'Virtio network device 1000' if=eth1 drv=virtio-pci unused=uio_pci_generic
Other Network devices
=====================
0000:00:09.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
0000:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
0000:00:0b.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
0000:00:0c.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
0000:00:0d.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
0000:00:0e.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' unused=uio_pci_generic
No 'Crypto' devices detected
============================
No 'Eventdev' devices detected
==============================
No 'Mempool' devices detected
=============================
No 'Compress' devices detected
==============================
But it wont bind them to the i40e driver:
root@10.129.182.229:~# dpdk-devbind -b i40e "0000:00:09.0"
Error: bind failed for 0000:00:09.0 - Cannot bind to driver i40e
I'm wondering what I can do to debug this?
Thanks,
Jeff
Disclaimer:
This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is considered confidential, proprietary, sensitive and/or otherwise legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.
next reply other threads:[~2019-09-10 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 19:49 Jeff Weeks [this message]
2019-09-11 16:30 ` Iremonger, Bernard
2019-09-12 0:48 ` Jeff Weeks
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=ef91c499cc7b4617a0474e80d7351b18@sandvine.com \
--to=jweeks@sandvine.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).