From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw158854-158855 [PATCH] [2/2] net/mlx5: fix the masked val
Date: Mon, 17 Nov 2025 12:56:25 -0800 (PST) [thread overview]
Message-ID: <691b8bf9.050a0220.3daff.3e76SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251117080942.9750-1-bingz@nvidia.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/158855
_Performance Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, November 17 2025 08:09:42
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:18d8a8909b8ed6b0a4bd8f99971da74ebba792e2
158854-158855 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#255429
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.7% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | 1.3% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34624/
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-17 20:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251117080942.9750-1-bingz@nvidia.com>
2025-11-17 7:48 ` |SUCCESS| pw158854-158855 [PATCH 2/2] net/mlx5: fix the masked value for a rule for sync API qemudev
2025-11-17 7:53 ` qemudev
2025-11-17 8:09 ` |WARNING| pw158855 " checkpatch
2025-11-17 9:19 ` |FAILURE| " 0-day Robot
2025-11-17 9:45 ` |SUCCESS| pw158854-158855 [PATCH] [2/2] net/mlx5: fix the masked val dpdklab
2025-11-17 9:45 ` |FAILURE| " dpdklab
2025-11-17 9:50 ` |SUCCESS| " dpdklab
2025-11-17 9:54 ` |FAILURE| " dpdklab
2025-11-17 10:12 ` |SUCCESS| " dpdklab
2025-11-17 11:50 ` |PENDING| " dpdklab
2025-11-17 12:48 ` |FAILURE| " dpdklab
2025-11-17 12:59 ` dpdklab
2025-11-17 13:00 ` dpdklab
2025-11-17 13:07 ` |SUCCESS| " dpdklab
2025-11-17 13:09 ` |FAILURE| " dpdklab
2025-11-17 13:09 ` dpdklab
2025-11-17 13:10 ` dpdklab
2025-11-17 13:13 ` dpdklab
2025-11-17 13:19 ` dpdklab
2025-11-17 13:20 ` dpdklab
2025-11-17 13:21 ` |PENDING| " dpdklab
2025-11-17 13:27 ` |FAILURE| " dpdklab
2025-11-17 13:33 ` dpdklab
2025-11-17 13:46 ` |PENDING| " dpdklab
2025-11-17 13:53 ` |FAILURE| " dpdklab
2025-11-17 14:14 ` dpdklab
2025-11-17 14:23 ` |WARNING| " dpdklab
2025-11-17 14:41 ` |FAILURE| " dpdklab
2025-11-17 14:45 ` dpdklab
2025-11-17 14:47 ` dpdklab
2025-11-17 14:59 ` dpdklab
2025-11-17 15:00 ` dpdklab
2025-11-17 15:01 ` dpdklab
2025-11-17 15:15 ` dpdklab
2025-11-17 15:15 ` |WARNING| " dpdklab
2025-11-17 15:16 ` |FAILURE| " dpdklab
2025-11-17 15:18 ` dpdklab
2025-11-17 15:19 ` dpdklab
2025-11-17 15:19 ` dpdklab
2025-11-17 15:24 ` dpdklab
2025-11-17 15:27 ` dpdklab
2025-11-17 15:29 ` dpdklab
2025-11-17 15:53 ` dpdklab
2025-11-17 15:58 ` dpdklab
2025-11-17 16:25 ` |SUCCESS| " dpdklab
2025-11-17 16:48 ` dpdklab
2025-11-17 18:07 ` dpdklab
2025-11-17 18:21 ` dpdklab
2025-11-17 19:09 ` dpdklab
2025-11-17 19:26 ` dpdklab
2025-11-17 20:56 ` dpdklab [this message]
2025-11-17 21:20 ` |FAILURE| " dpdklab
2025-11-17 22:28 ` |WARNING| " 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=691b8bf9.050a0220.3daff.3e76SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).