From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139277 [PATCH] [v5] ethdev: fix strict aliasing lead to
Date: Sat, 13 Apr 2024 02:06:49 -0700 (PDT) [thread overview]
Message-ID: <661a4b29.050a0220.365f6.e229SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240413080440.19831-1-fengchengwen@huawei.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/139277
_Performance Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Saturday, April 13 2024 08:04:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6db5f91b5e628671c341b833f21ea35e65e9699d
139277 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29772/
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:[~2024-04-13 9:06 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240413080440.19831-1-fengchengwen@huawei.com>
2024-04-13 7:43 ` |SUCCESS| pw139277 [PATCH v5] ethdev: fix strict aliasing lead to link cannot be up qemudev
2024-04-13 7:48 ` qemudev
2024-04-13 8:08 ` checkpatch
2024-04-13 8:57 ` |SUCCESS| pw139277 [PATCH] [v5] ethdev: fix strict aliasing lead to dpdklab
2024-04-13 8:58 ` dpdklab
2024-04-13 8:58 ` dpdklab
2024-04-13 8:59 ` dpdklab
2024-04-13 8:59 ` dpdklab
2024-04-13 8:59 ` dpdklab
2024-04-13 9:00 ` dpdklab
2024-04-13 9:00 ` dpdklab
2024-04-13 9:00 ` dpdklab
2024-04-13 9:01 ` dpdklab
2024-04-13 9:01 ` dpdklab
2024-04-13 9:01 ` dpdklab
2024-04-13 9:02 ` dpdklab
2024-04-13 9:02 ` dpdklab
2024-04-13 9:02 ` dpdklab
2024-04-13 9:03 ` dpdklab
2024-04-13 9:04 ` dpdklab
2024-04-13 9:05 ` dpdklab
2024-04-13 9:06 ` dpdklab
2024-04-13 9:06 ` dpdklab [this message]
2024-04-13 9:06 ` dpdklab
2024-04-13 9:07 ` dpdklab
2024-04-13 9:07 ` dpdklab
2024-04-13 9:08 ` dpdklab
2024-04-13 9:08 ` dpdklab
2024-04-13 9:08 ` dpdklab
2024-04-13 9:08 ` dpdklab
2024-04-13 9:09 ` dpdklab
2024-04-13 9:09 ` dpdklab
2024-04-13 9:09 ` dpdklab
2024-04-13 9:10 ` dpdklab
2024-04-13 9:10 ` dpdklab
2024-04-13 9:10 ` dpdklab
2024-04-13 9:11 ` dpdklab
2024-04-13 9:11 ` dpdklab
2024-04-13 9:11 ` dpdklab
2024-04-13 9:11 ` dpdklab
2024-04-13 9:12 ` dpdklab
2024-04-13 9:12 ` dpdklab
2024-04-13 9:13 ` dpdklab
2024-04-13 9:19 ` dpdklab
2024-04-13 9:19 ` dpdklab
2024-04-13 9:19 ` dpdklab
2024-04-13 9:19 ` dpdklab
2024-04-13 9:19 ` dpdklab
2024-04-13 9:28 ` dpdklab
2024-04-13 9:28 ` dpdklab
2024-04-13 9:29 ` dpdklab
2024-04-13 9:37 ` dpdklab
2024-04-13 9:37 ` dpdklab
2024-04-13 9:38 ` dpdklab
2024-04-13 9:39 ` dpdklab
2024-04-13 9:39 ` dpdklab
2024-04-13 9:40 ` dpdklab
2024-04-13 9:40 ` dpdklab
2024-04-13 9:40 ` dpdklab
2024-04-13 9:41 ` dpdklab
2024-04-13 9:41 ` dpdklab
2024-04-13 9:42 ` dpdklab
2024-04-13 9:45 ` dpdklab
2024-04-13 9:46 ` dpdklab
2024-04-13 9:46 ` dpdklab
2024-04-13 9:48 ` dpdklab
2024-04-13 9:49 ` dpdklab
2024-04-13 9:50 ` dpdklab
2024-04-13 9:50 ` dpdklab
2024-04-13 9:51 ` dpdklab
2024-04-13 9:57 ` dpdklab
2024-04-13 10:12 ` dpdklab
2024-04-13 10:12 ` dpdklab
2024-04-13 10:15 ` dpdklab
2024-04-13 10:20 ` dpdklab
2024-04-13 10:30 ` dpdklab
2024-04-13 10:33 ` dpdklab
2024-04-13 10:33 ` dpdklab
2024-04-13 10:53 ` dpdklab
2024-04-13 10:53 ` dpdklab
2024-04-13 11:00 ` dpdklab
2024-04-13 11:09 ` dpdklab
2024-04-13 11:14 ` 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=661a4b29.050a0220.365f6.e229SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.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).