From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138011 [PATCH] net/hns3: support new device
Date: Wed, 06 Mar 2024 04:38:40 -0800 (PST) [thread overview]
Message-ID: <65e863d0.050a0220.b5cf2.1144SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306092112.506493-1-haijie1@huawei.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138011
_Performance Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Wednesday, March 06 2024 09:21:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:bd4ce75c651612bd9dc395315d10b1a39ba78248
138011 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-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.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.8% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29433/
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-03-06 12:38 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306092112.506493-1-haijie1@huawei.com>
2024-03-06 9:02 ` qemudev
2024-03-06 9:06 ` qemudev
2024-03-06 9:26 ` checkpatch
2024-03-06 10:24 ` 0-day Robot
2024-03-06 12:20 ` dpdklab
2024-03-06 12:21 ` dpdklab
2024-03-06 12:22 ` dpdklab
2024-03-06 12:22 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:37 ` dpdklab
2024-03-06 12:38 ` dpdklab [this message]
2024-03-06 12:38 ` dpdklab
2024-03-06 12:43 ` dpdklab
2024-03-06 12:49 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 13:16 ` dpdklab
2024-03-06 13:17 ` dpdklab
2024-03-06 13:17 ` dpdklab
2024-03-06 13:18 ` dpdklab
2024-03-06 13:18 ` dpdklab
2024-03-06 13:19 ` dpdklab
2024-03-06 14:01 ` dpdklab
2024-03-06 14:03 ` dpdklab
2024-03-06 14:05 ` dpdklab
2024-03-06 14:10 ` dpdklab
2024-03-06 14:11 ` dpdklab
2024-03-06 14:11 ` dpdklab
2024-03-06 14:13 ` dpdklab
2024-03-06 14:13 ` dpdklab
2024-03-06 14:14 ` dpdklab
2024-03-06 14:15 ` dpdklab
2024-03-06 14:15 ` dpdklab
2024-03-06 14:25 ` dpdklab
2024-03-06 14:26 ` dpdklab
2024-03-06 14:27 ` dpdklab
2024-03-06 14:38 ` dpdklab
2024-03-06 14:49 ` dpdklab
2024-03-06 14:50 ` dpdklab
2024-03-06 14:51 ` dpdklab
2024-03-06 14:52 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:55 ` dpdklab
2024-03-06 15:05 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:14 ` dpdklab
2024-03-06 15:15 ` dpdklab
2024-03-06 15:16 ` dpdklab
2024-03-06 15:17 ` dpdklab
2024-03-06 15:18 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:23 ` dpdklab
2024-03-06 15:26 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:36 ` dpdklab
2024-03-06 15:44 ` dpdklab
2024-03-06 16:21 ` dpdklab
2024-03-06 16:25 ` dpdklab
2024-03-06 17:29 ` dpdklab
2024-03-06 19:46 ` 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=65e863d0.050a0220.b5cf2.1144SMTPIN_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).