From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: david.marchand@redhat.com
Subject: |SUCCESS|dpdk|8c4861d00a| Intel-Testing
Date: 04 Nov 2025 03:16:49 -0800 [thread overview]
Message-ID: <e04965$5mbnjs@ORVIESA003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3722 bytes --]
Test-Label: intel-Testing
Test-Status: SUCCESS
_Testing PASS_
DPDK git repo: dpdk
commit 4bd1a50a0791e7e2a0d1719114150d262f82cc21
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Nov 4 11:02:14 2025 +0100
mbuf: dump Tx offload metadata
When debugging TSO and other checksum offloads, dumping the various
l*_len fields and TSO segmentation size can be helpful.
Example in OVS that dumps a mbuf on rte_eth_tx_prepare failure:
Before:
netdev_dpdk(pmd-c30/id:11)|DBG|dpdk0: First invalid packet:
dump mbuf at 0x2201a916c0, iova=0x2200800580, buf_len=6864
pkt_len=6804, ol_flags=0x3114800000000102, nb_segs=1, port=65535, ptype=0
segment at 0x2201a916c0, data=0x22008005b2, len=6804, off=50, refcnt=1
Dump data at [0x22008005b2], len=6804
...
After:
netdev_dpdk(pmd-c30/id:11)|DBG|dpdk0: First invalid packet:
dump mbuf at 0x2201a916c0, iova=0x2200800580, buf_len=6864, pkt_len=6804
outer_l2_len=14, outer_l3_len=40, l2_len=38, l3_len=40, l4_len=32
ol_flags=0x3114800000000102, nb_segs=1, port=65535, ptype=0
segment at 0x2201a916c0, data=0x22008005b2, len=6804, off=50, refcnt=1
Dump data at [0x22008005b2], len=6804
...
Signed-off-by: David Marchand <david.marchand@redhat.com>
Testing Summary : 18 Case Done, 18 Successful, 0 Failures
TestPlan:
pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst
TestSuite:
pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
OS : Ubuntu 22.04.5 LTS
Kernel : 6.8.0-40-generic
GCC : 11.4.0-1ubuntu1~22.04.2
NIC : Ethernet Controller E810-C for SFP
Target : x86_64-native-linuxapp-gcc
Test result details:
+-------------+---------------------------+-------+
| suite | case | status|
+-------------+---------------------------+-------+
| asan_smoke | test_rxtx_with_ASan_enable| passed|
| pf_smoke | test_pf_jumbo_frames | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_jumbo_frames | n/a |
| virtio_smoke| test_virtio_loopback | passed|
| virtio_smoke| test_virtio_pvp | passed|
+-------------+---------------------------+-------+
OS : Ubuntu 22.04.5 LTS
Kernel : 5.15.0-119-generic
GCC : 11.4.0-1ubuntu1~22.04.2
NIC : Ethernet Controller XL710 for 40GbE QSFP+
Target : x86_64-native-linuxapp-gcc
Test result details:
+-------------+---------------------------+-------+
| suite | case | status|
+-------------+---------------------------+-------+
| asan_smoke | test_rxtx_with_ASan_enable| passed|
| pf_smoke | test_pf_jumbo_frames | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_jumbo_frames | n/a |
| virtio_smoke| test_virtio_loopback | passed|
| virtio_smoke| test_virtio_pvp | passed|
+-------------+---------------------------+-------+
DPDK STV team
next reply other threads:[~2025-11-04 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 11:16 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-03 20:20 sys_stv
2025-11-03 17:44 sys_stv
2025-11-01 20:37 sys_stv
2025-11-01 17:49 sys_stv
2025-10-31 12:05 sys_stv
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='e04965$5mbnjs@ORVIESA003-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=david.marchand@redhat.com \
--cc=test-report@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).