From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: |SUCCESS| pw158817 [PATCH] net/bnxt: fix unintialized warning
Date: Fri, 21 Nov 2025 09:40:58 -0800 (PST) [thread overview]
Message-ID: <6920a42a.050a0220.36db3d.3ddcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251114185240.1363648-1-stephen@networkplumber.org>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/158817
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, November 14 2025 18:52:40
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: master
CommitID:bfb6c9fbcbaada197af422b704cf71b777f85fff
158817 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#255939
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34599/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-11-21 17:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251114185240.1363648-1-stephen@networkplumber.org>
2025-11-14 18:17 ` qemudev
2025-11-14 18:25 ` |FAILURE| " qemudev
2025-11-14 18:52 ` |WARNING| " checkpatch
2025-11-14 20:29 ` |SUCCESS| " 0-day Robot
2025-11-14 20:29 ` 0-day Robot
2025-11-21 16:10 ` |PENDING| " dpdklab
2025-11-21 16:13 ` dpdklab
2025-11-21 16:15 ` dpdklab
2025-11-21 16:18 ` |SUCCESS| " dpdklab
2025-11-21 16:19 ` |PENDING| " dpdklab
2025-11-21 16:22 ` dpdklab
2025-11-21 16:24 ` |SUCCESS| " dpdklab
2025-11-21 16:34 ` dpdklab
2025-11-21 16:35 ` dpdklab
2025-11-21 17:05 ` dpdklab
2025-11-21 17:11 ` dpdklab
2025-11-21 17:21 ` dpdklab
2025-11-21 17:31 ` dpdklab
2025-11-21 17:40 ` dpdklab [this message]
2025-11-21 17:52 ` dpdklab
2025-11-21 19:19 ` dpdklab
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=6920a42a.050a0220.36db3d.3ddcSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).