From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142752 [PATCH] hash: separate param checks in hash creat
Date: Tue, 30 Jul 2024 06:01:25 -0700 (PDT) [thread overview]
Message-ID: <66a8e425.050a0220.22ebab.d3f3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240726145443.1058676-1-niall.meade@intel.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142752
_Performance Testing PASS_
Submitter: Niall Meade <niall.meade@intel.com>
Date: Friday, July 26 2024 14:54:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4b5abe7ec1ed2d43a285599bbba23f62ac049d8f
142752 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#171623
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.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 | 256 | 1 | 1 | -0.7% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30648/
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-07-30 14:41 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240726145443.1058676-1-niall.meade@intel.com>
2024-07-30 6:42 ` |SUCCESS| pw142752 [PATCH] hash: separate param checks in hash create func qemudev
2024-07-30 6:47 ` qemudev
2024-07-30 7:09 ` checkpatch
2024-07-30 13:01 ` dpdklab [this message]
2024-07-30 13:14 ` |SUCCESS| pw142752 [PATCH] hash: separate param checks in hash creat dpdklab
2024-07-30 13:17 ` dpdklab
2024-07-30 13:22 ` dpdklab
2024-07-30 13:24 ` dpdklab
2024-07-30 13:30 ` dpdklab
2024-07-30 13:36 ` |PENDING| " dpdklab
2024-07-30 13:36 ` |SUCCESS| " dpdklab
2024-07-30 13:37 ` dpdklab
2024-07-30 13:38 ` |PENDING| " dpdklab
2024-07-30 13:44 ` dpdklab
2024-07-30 13:44 ` |SUCCESS| " dpdklab
2024-07-30 13:45 ` |PENDING| " dpdklab
2024-07-30 13:45 ` dpdklab
2024-07-30 13:52 ` |SUCCESS| " dpdklab
2024-07-30 13:52 ` |PENDING| " dpdklab
2024-07-30 13:54 ` dpdklab
2024-07-30 13:56 ` dpdklab
2024-07-30 13:56 ` dpdklab
2024-07-30 13:58 ` dpdklab
2024-07-30 13:59 ` dpdklab
2024-07-30 14:00 ` dpdklab
2024-07-30 14:01 ` dpdklab
2024-07-30 14:01 ` dpdklab
2024-07-30 14:01 ` dpdklab
2024-07-30 14:02 ` dpdklab
2024-07-30 14:03 ` dpdklab
2024-07-30 14:04 ` dpdklab
2024-07-30 14:04 ` dpdklab
2024-07-30 14:05 ` dpdklab
2024-07-30 14:08 ` dpdklab
2024-07-30 14:08 ` |SUCCESS| " dpdklab
2024-07-30 14:09 ` dpdklab
2024-07-30 14:10 ` |PENDING| " dpdklab
2024-07-30 14:11 ` dpdklab
2024-07-30 14:13 ` dpdklab
2024-07-30 14:13 ` dpdklab
2024-07-30 14:16 ` dpdklab
2024-07-30 14:19 ` dpdklab
2024-07-30 14:20 ` dpdklab
2024-07-30 14:23 ` dpdklab
2024-07-30 14:24 ` dpdklab
2024-07-30 14:26 ` |SUCCESS| " dpdklab
2024-07-30 14:28 ` dpdklab
2024-07-30 14:29 ` dpdklab
2024-07-30 14:29 ` |PENDING| " dpdklab
2024-07-30 14:30 ` dpdklab
2024-07-30 14:31 ` |SUCCESS| " dpdklab
2024-07-30 14:32 ` |PENDING| " dpdklab
2024-07-30 14:33 ` dpdklab
2024-07-30 14:35 ` |SUCCESS| " dpdklab
2024-07-30 14:36 ` |PENDING| " dpdklab
2024-07-30 14:36 ` dpdklab
2024-07-30 14:37 ` dpdklab
2024-07-30 14:40 ` dpdklab
2024-07-30 14:40 ` dpdklab
2024-07-30 14:42 ` dpdklab
2024-07-30 14:43 ` dpdklab
2024-07-30 14:45 ` dpdklab
2024-07-30 14:46 ` dpdklab
2024-07-30 14:49 ` dpdklab
2024-07-30 14:50 ` |SUCCESS| " dpdklab
2024-07-30 14:53 ` dpdklab
2024-07-30 14:54 ` |PENDING| " dpdklab
2024-07-30 14:54 ` dpdklab
2024-07-30 14:55 ` |SUCCESS| " dpdklab
2024-07-30 14:56 ` |PENDING| " dpdklab
2024-07-30 14:57 ` dpdklab
2024-07-30 14:58 ` dpdklab
2024-07-30 14:59 ` |SUCCESS| " dpdklab
2024-07-30 14:59 ` |PENDING| " dpdklab
2024-07-30 15:00 ` dpdklab
2024-07-30 15:01 ` dpdklab
2024-07-30 15:02 ` dpdklab
2024-07-30 15:02 ` dpdklab
2024-07-30 15:03 ` dpdklab
2024-07-30 15:04 ` dpdklab
2024-07-30 15:05 ` dpdklab
2024-07-30 15:06 ` dpdklab
2024-07-30 15:07 ` dpdklab
2024-07-30 15:07 ` dpdklab
2024-07-30 15:08 ` dpdklab
2024-07-30 15:08 ` dpdklab
2024-07-30 15:08 ` dpdklab
2024-07-30 15:09 ` dpdklab
2024-07-30 15:10 ` |SUCCESS| " dpdklab
2024-07-30 15:11 ` dpdklab
2024-07-30 15:21 ` |PENDING| " dpdklab
2024-07-30 15:23 ` dpdklab
2024-07-30 15:23 ` dpdklab
2024-07-30 15:26 ` dpdklab
2024-07-30 15:28 ` dpdklab
2024-07-30 15:29 ` dpdklab
2024-07-30 15:30 ` dpdklab
2024-07-30 15:31 ` dpdklab
2024-07-30 15:37 ` dpdklab
2024-07-30 15:40 ` dpdklab
2024-07-30 15:42 ` dpdklab
2024-07-30 15:43 ` dpdklab
2024-07-30 15:43 ` dpdklab
2024-07-30 15:44 ` dpdklab
2024-07-30 15:45 ` dpdklab
2024-07-30 15:48 ` dpdklab
2024-07-30 15:51 ` dpdklab
2024-07-30 15:53 ` |SUCCESS| " dpdklab
2024-07-30 16:06 ` |PENDING| " dpdklab
2024-07-30 16:15 ` dpdklab
2024-07-30 16:23 ` dpdklab
2024-07-30 16:30 ` |SUCCESS| " dpdklab
2024-07-30 17:04 ` 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=66a8e425.050a0220.22ebab.d3f3SMTPIN_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).