From: Thomas DETHIER <t.dethier@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Subject: DPDK can not detect E810-CQDA2 on Ubuntu 20.04
Date: Mon, 16 May 2022 09:28:25 +0000 [thread overview]
Message-ID: <001b21c779cc4b33bf5a059f8694d562@deltacast.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Hello,
I have been experiencing issues with an Intel E810-CQDA2 and Ubuntu Server 20.04 on DPDK 21.10 and 22.03 :
Command used :
sudo ./dpdk-testpmd -l 1-7 -n 4 -a 17:00.0 -- --socket-num=0 --burst=10 --txd=1024 --rxd=1024 --mbcache=512 --rxq=1 --txq=1 --nb-cores=1 --txpkts=1500 -i --txonly-multi-flow --forward-mode=txonly --tx-ip=10.10.1.168,239.0.0.8
Output:
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Fail: input rxq (1) can't be greater than max_rx_queues (0) of port 0
EAL: Error - exiting with code: 1
Cause: rxq 1 invalid - must be >= 0 && <= 0
It seem that the Nic isn't detected by DPDK when running the tests, but when I run dpdk-devbind
$ dpdk-devbind.py -s
Network devices using DPDK-compatible driver
============================================
0000:17:00.0 'Ethernet Controller E810-C for QSFP 1592' drv=igb_uio unused=ice,vfio-pci
I don't understand why I can't use the device although it is binded to DPDK.
Thanks for your help,
Thomas DETHIER | Test Project Engineer | DELTACAST.TV
t.dethier@deltacast.tv<mailto:t.dethier@deltacast.tv>
www.deltacast.tv<http://www.deltacast.tv>
[-- Attachment #2: Type: text/html, Size: 6979 bytes --]
next reply other threads:[~2022-05-16 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 9:28 Thomas DETHIER [this message]
2022-05-19 13:20 Yasin CANER
2022-05-23 12:00 ` Thomas DETHIER
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=001b21c779cc4b33bf5a059f8694d562@deltacast.tv \
--to=t.dethier@deltacast.tv \
--cc=users@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).