From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/testpmd Bug 1797] [dpdk-25.11-rc0] rxtx_offload/txoffload_port_multi_segs: set multi segs failed
Date: Tue, 30 Sep 2025 02:57:31 +0000 [thread overview]
Message-ID: <bug-1797-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1797
Bug ID: 1797
Summary: [dpdk-25.11-rc0]
rxtx_offload/txoffload_port_multi_segs: set multi segs
failed
Product: DPDK
Version: unspecified
Hardware: All
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: hailinx.xu@intel.com
Target Milestone: ---
ENV:
====
DPDK version: dpdk25.11.0-rc0: 1d627ea13aeec2bcccf27246e6be2508370d171e
OS: FreeBSD 14.3-RELEASE/14.3-RELEASE
Compiler: gcc version 13.3.0 (FreeBSD Ports Collection)
Hardware platform: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
NIC hardware:Intel Corporation Ethernet Controller E810-C for SFP
NIC firmware:
Driver: ice-2.0.9
NVM: nvm 4.90 etid 80020f02 netlist 4.4.2000-1.17.0.dfc6695b oem 1.3863.0
DDP: ICE OS Default Package version 1.3.44.0
step:
=====
1. bind ports to DPDK
kenv hw.nic_uio.bdfs="75:0:0,75:0:1,75:0:2,75:0:3"
kldload ./x86_64-native-bsdapp-gcc/kmod/nic_uio.ko 2. exit testpmd
2. Launch testpmd x86_64-native-bsdapp-gcc/app/dpdk-testpmd -l 0,2,4,28 -n 4 -a
0000:4b:00.0 -a 0000:4b:00.1 -a 0000:4b:00.2 -a 0000:4b:00.3 -- -i
port stop all
port config 0 tx_offload multi_segs on
port config 1 tx_offload multi_segs on
port config 2 tx_offload multi_segs on
port config 3 tx_offload multi_segs on
port start all
port start 0
output
======
Configuring Port 0 (socket 0)
ETHDEV: id=0 offload clash, MULTI_SEGS vs MBUF_FAST_FREE
Fail to configure port 0
Expected Result
===============
testpmd> show port 0 tx_offload configuration
Tx Offloading Configuration of port 0 :
Port : MULTI_SEGS
Queue[ 0] : MULTI_SEGS
bad commit
==========
commit fdb840367cf0d6abeb17b05623679b8d1ea4c902
Author: Morten Brørup <mb@smartsharesystems.com>
Date: Sun Aug 3 19:42:18 2025 +0000
ethdev: reject conflicting Tx offload configurations
When an ethdev port is configured for fast mbuf release, the driver can
use a Tx burst function relying on the fast mbuf release preconditions.
Thus, also configuring this port or a queue on the port for transmitting
segmented packets is prohibited.
Checks for these conflicting configurations have been added to the ethdev
library, so the drivers don't have to implement them.
Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-09-30 2:57 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=bug-1797-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).