From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159584 [PATCH] net/mlx5: fix MPESW PF probe
Date: Fri, 09 Jan 2026 18:17:01 -0800 (PST) [thread overview]
Message-ID: <6961b69d.050a0220.1eb552.bacaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260105132941.72705-1-bingz@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/159584
_Performance Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, January 05 2026 13:29:41
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:1b8a03f181d93c751ebea9df1584628f485ec745
159584 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#260302
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.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
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.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34809/
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:[~2026-01-10 2:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260105132941.72705-1-bingz@nvidia.com>
2026-01-05 13:01 ` qemudev
2026-01-05 13:06 ` qemudev
2026-01-05 13:31 ` checkpatch
2026-01-05 14:24 ` 0-day Robot
2026-01-05 14:24 ` 0-day Robot
2026-01-08 1:26 ` dpdklab
2026-01-08 1:37 ` dpdklab
2026-01-08 6:58 ` |PENDING| " dpdklab
2026-01-08 21:13 ` |SUCCESS| " dpdklab
2026-01-08 21:13 ` dpdklab
2026-01-08 21:14 ` dpdklab
2026-01-08 21:15 ` dpdklab
2026-01-08 21:17 ` dpdklab
2026-01-08 21:17 ` dpdklab
2026-01-08 21:18 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 22:25 ` dpdklab
2026-01-08 22:40 ` dpdklab
2026-01-08 23:45 ` dpdklab
2026-01-08 23:45 ` dpdklab
2026-01-08 23:47 ` dpdklab
2026-01-09 13:03 ` |FAILURE| " dpdklab
2026-01-09 19:31 ` |SUCCESS| " dpdklab
2026-01-10 2:17 ` dpdklab [this message]
2026-01-10 2:34 ` 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=6961b69d.050a0220.1eb552.bacaSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).