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| pw139455 [PATCH] [v3] mailmap: clean up vmware entries
Date: Wed, 17 Apr 2024 19:39:08 -0700 (PDT) [thread overview]
Message-ID: <662087cc.0d0a0220.b57b1.24feSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417161901.1919433-1-jochen.behrens@broadcom.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/139455
_Performance Testing PASS_
Submitter: Jochen Behrens <jochen.behrens@broadcom.com>
Date: Wednesday, April 17 2024 16:19:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139455 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29809/
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-18 2:39 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417161901.1919433-1-jochen.behrens@broadcom.com>
2024-04-17 15:56 ` |SUCCESS| pw139455 [PATCH v3] " qemudev
2024-04-17 16:00 ` qemudev
2024-04-17 16:19 ` |WARNING| " checkpatch
2024-04-17 17:24 ` |SUCCESS| " 0-day Robot
2024-04-18 2:33 ` |SUCCESS| pw139455 [PATCH] [v3] " dpdklab
2024-04-18 2:33 ` dpdklab
2024-04-18 2:34 ` dpdklab
2024-04-18 2:36 ` dpdklab
2024-04-18 2:36 ` dpdklab
2024-04-18 2:37 ` dpdklab
2024-04-18 2:38 ` dpdklab
2024-04-18 2:39 ` dpdklab [this message]
2024-04-18 2:39 ` dpdklab
2024-04-18 2:42 ` dpdklab
2024-04-18 2:43 ` dpdklab
2024-04-18 2:43 ` dpdklab
2024-04-18 2:44 ` dpdklab
2024-04-18 2:44 ` dpdklab
2024-04-18 2:46 ` dpdklab
2024-04-18 2:47 ` dpdklab
2024-04-18 2:52 ` dpdklab
2024-04-18 2:53 ` dpdklab
2024-04-18 2:56 ` dpdklab
2024-04-18 3:11 ` dpdklab
2024-04-18 3:17 ` dpdklab
2024-04-18 3:18 ` dpdklab
2024-04-18 3:19 ` dpdklab
2024-04-18 3:19 ` dpdklab
2024-04-18 3:19 ` dpdklab
2024-04-18 3:20 ` dpdklab
2024-04-18 3:21 ` dpdklab
2024-04-18 3:21 ` dpdklab
2024-04-18 3:21 ` dpdklab
2024-04-18 3:21 ` dpdklab
2024-04-18 3:21 ` dpdklab
2024-04-18 3:22 ` dpdklab
2024-04-18 3:22 ` dpdklab
2024-04-18 3:22 ` dpdklab
2024-04-18 3:22 ` dpdklab
2024-04-18 3:23 ` dpdklab
2024-04-18 3:23 ` dpdklab
2024-04-18 3:23 ` dpdklab
2024-04-18 3:23 ` dpdklab
2024-04-18 3:23 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:24 ` dpdklab
2024-04-18 3:25 ` dpdklab
2024-04-18 3:25 ` dpdklab
2024-04-18 3:25 ` dpdklab
2024-04-18 3:25 ` dpdklab
2024-04-18 3:25 ` dpdklab
2024-04-18 3:26 ` dpdklab
2024-04-18 3:26 ` dpdklab
2024-04-18 3:26 ` dpdklab
2024-04-18 3:26 ` dpdklab
2024-04-18 3:27 ` dpdklab
2024-04-18 3:27 ` dpdklab
2024-04-18 3:27 ` dpdklab
2024-04-18 3:27 ` dpdklab
2024-04-18 3:28 ` dpdklab
2024-04-18 3:30 ` dpdklab
2024-04-18 3:31 ` dpdklab
2024-04-18 3:37 ` dpdklab
2024-04-18 3:39 ` dpdklab
2024-04-18 3:45 ` dpdklab
2024-04-18 3:49 ` dpdklab
2024-04-18 3:53 ` dpdklab
2024-04-18 3:58 ` dpdklab
2024-04-18 4:00 ` dpdklab
2024-04-18 4:01 ` dpdklab
2024-04-18 4:02 ` dpdklab
2024-04-18 4:10 ` dpdklab
2024-04-18 4:11 ` dpdklab
2024-04-18 4:11 ` dpdklab
2024-04-18 4:11 ` dpdklab
2024-04-18 4:11 ` dpdklab
2024-04-18 4:23 ` dpdklab
2024-04-18 4:47 ` dpdklab
2024-04-18 4:49 ` dpdklab
2024-04-18 4:49 ` dpdklab
2024-04-18 4:58 ` dpdklab
2024-04-18 5:36 ` dpdklab
2024-04-18 5:42 ` 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=662087cc.0d0a0220.b57b1.24feSMTPIN_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).