From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1069] Testpmd parameter --enable-lro fails on Mellanox ConnectX-5
Date: Fri, 19 Aug 2022 07:49:32 +0000 [thread overview]
Message-ID: <bug-1069-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1069
Bug ID: 1069
Summary: Testpmd parameter --enable-lro fails on Mellanox
ConnectX-5
Product: DPDK
Version: 22.03
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: liangxing.wang@arm.com
Target Milestone: ---
User tried to enable lro for Mellanox ConnectX5 (MT27800) card through below
dpdk testpmd cmd:
#################
sudo ./dpdk-testpmd -l 15-16 -a 0000:01:00.0,dv_flow_en=1 -v -- --txq=1
--rxq=1 --enable-lro -i
but always encountered below error:
#####################
EAL: Detected CPU lcores: 80
EAL: Detected NUMA nodes: 1
EAL: RTE Version: 'DPDK 22.03.0'
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 32 hugepages of size 1073741824 reserved, but no mount
ed hugetlbfs found for that size
EAL: VFIO support initialized
EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:01
:00.0 (socket 0)
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, size
=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Warning! port-topology=paired and odd forward ports number,
the last port will pair with itself.
Configuring Port 0 (socket 0)
Ethdev port_id=0 requested Rx offloads 0x10 doesn't match R
x offloads capabilities 0x19620f in rte_eth_dev_configure()
Fail to configure port 0
EAL: Error - exiting with code: 1
Cause: Start ports failed
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-08-19 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 7:49 bugzilla [this message]
2022-08-19 8:42 ` [Bug 1069] Testpmd parameter --enable-lro fails on Mellanox ConnectX-5 Asaf Penso
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=bug-1069-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).