From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142274-142275 [PATCH] [v1,2/2] dts: improve starting and
Date: Tue, 09 Jul 2024 11:13:12 -0700 (PDT) [thread overview]
Message-ID: <668d7db8.170a0220.19252.41dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240709163145.110030-3-jspewock@iol.unh.edu>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142275
_Performance Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tuesday, July 09 2024 16:31:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e8aa4a4f90dce1fcea03a93f508e3d9bc0c98c0
142274-142275 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: Unknown
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 1.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 2.7% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30481/
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-09 18:13 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240709163145.110030-3-jspewock@iol.unh.edu>
2024-07-09 16:06 ` |SUCCESS| pw142274-142275 [PATCH v1 2/2] dts: improve starting and stopping interactive shells qemudev
2024-07-09 16:10 ` qemudev
2024-07-09 16:32 ` |SUCCESS| pw142275 " checkpatch
2024-07-09 17:23 ` 0-day Robot
2024-07-09 17:55 ` |PENDING| pw142274-142275 [PATCH] [v1,2/2] dts: improve starting and dpdklab
2024-07-09 18:01 ` |SUCCESS| " dpdklab
2024-07-09 18:05 ` dpdklab
2024-07-09 18:10 ` |PENDING| " dpdklab
2024-07-09 18:13 ` dpdklab [this message]
2024-07-09 18:15 ` |SUCCESS| " dpdklab
2024-07-09 18:16 ` |PENDING| " dpdklab
2024-07-09 18:17 ` dpdklab
2024-07-09 18:18 ` |SUCCESS| " dpdklab
2024-07-09 18:18 ` |PENDING| " dpdklab
2024-07-09 18:21 ` |SUCCESS| " dpdklab
2024-07-09 18:22 ` |PENDING| " dpdklab
2024-07-09 18:22 ` dpdklab
2024-07-09 18:23 ` dpdklab
2024-07-09 18:24 ` |SUCCESS| " dpdklab
2024-07-09 18:26 ` dpdklab
2024-07-09 18:26 ` dpdklab
2024-07-09 18:28 ` |PENDING| " dpdklab
2024-07-09 18:28 ` dpdklab
2024-07-09 18:35 ` dpdklab
2024-07-09 18:35 ` dpdklab
2024-07-09 18:40 ` dpdklab
2024-07-09 18:40 ` dpdklab
2024-07-09 18:44 ` dpdklab
2024-07-09 18:49 ` dpdklab
2024-07-09 18:51 ` dpdklab
2024-07-09 18:53 ` dpdklab
2024-07-09 18:53 ` dpdklab
2024-07-09 18:53 ` dpdklab
2024-07-09 18:55 ` |SUCCESS| " dpdklab
2024-07-09 19:01 ` |PENDING| " dpdklab
2024-07-09 19:02 ` dpdklab
2024-07-09 19:03 ` dpdklab
2024-07-09 19:07 ` dpdklab
2024-07-09 19:13 ` |SUCCESS| " dpdklab
2024-07-09 23:23 ` |PENDING| " dpdklab
2024-07-10 4:33 ` dpdklab
2024-07-10 4:54 ` |SUCCESS| " dpdklab
2024-07-10 5:50 ` |PENDING| " dpdklab
2024-07-10 5:50 ` dpdklab
2024-07-10 5:51 ` dpdklab
2024-07-10 5:55 ` |SUCCESS| " dpdklab
2024-07-10 5:57 ` |PENDING| " dpdklab
2024-07-10 5:57 ` dpdklab
2024-07-10 5:58 ` dpdklab
2024-07-10 5:58 ` dpdklab
2024-07-10 5:59 ` dpdklab
2024-07-10 6:01 ` dpdklab
2024-07-10 6:02 ` dpdklab
2024-07-10 6:05 ` dpdklab
2024-07-10 6:08 ` |SUCCESS| " dpdklab
2024-07-10 6:08 ` |PENDING| " dpdklab
2024-07-10 6:12 ` dpdklab
2024-07-10 6:12 ` dpdklab
2024-07-10 6:14 ` dpdklab
2024-07-10 6:15 ` dpdklab
2024-07-10 6:16 ` dpdklab
2024-07-10 6:17 ` dpdklab
2024-07-10 6:26 ` dpdklab
2024-07-10 6:27 ` dpdklab
2024-07-10 6:27 ` dpdklab
2024-07-10 6:29 ` dpdklab
2024-07-10 6:30 ` dpdklab
2024-07-10 6:32 ` dpdklab
2024-07-10 6:33 ` dpdklab
2024-07-10 6:33 ` |SUCCESS| " dpdklab
2024-07-10 6:35 ` |PENDING| " dpdklab
2024-07-10 6:38 ` dpdklab
2024-07-10 6:41 ` dpdklab
2024-07-10 6:44 ` dpdklab
2024-07-10 6:48 ` dpdklab
2024-07-10 6:50 ` dpdklab
2024-07-10 6:51 ` dpdklab
2024-07-10 7:44 ` dpdklab
2024-07-10 7:58 ` dpdklab
2024-07-10 8:03 ` dpdklab
2024-07-10 8:17 ` |SUCCESS| " dpdklab
2024-07-10 15:52 ` |PENDING| " dpdklab
2024-07-10 15:53 ` dpdklab
2024-07-10 15:54 ` dpdklab
2024-07-10 15:55 ` dpdklab
2024-07-10 15:57 ` dpdklab
2024-07-10 15:57 ` dpdklab
2024-07-10 16:00 ` dpdklab
2024-07-10 16:00 ` dpdklab
2024-07-10 16:02 ` dpdklab
2024-07-10 16:03 ` dpdklab
2024-07-10 16:04 ` dpdklab
2024-07-10 16:05 ` dpdklab
2024-07-10 16:09 ` dpdklab
2024-07-10 16:09 ` dpdklab
2024-07-10 16:09 ` dpdklab
2024-07-10 16:11 ` dpdklab
2024-07-10 16:12 ` dpdklab
2024-07-10 16:12 ` dpdklab
2024-07-10 16:12 ` dpdklab
2024-07-10 16:13 ` dpdklab
2024-07-10 16:17 ` |SUCCESS| " dpdklab
2024-07-10 16:18 ` |PENDING| " dpdklab
2024-07-10 16:25 ` dpdklab
2024-07-10 16:25 ` dpdklab
2024-07-10 16:32 ` dpdklab
2024-07-10 16:32 ` dpdklab
2024-07-10 16:32 ` dpdklab
2024-07-10 16:38 ` dpdklab
2024-07-10 16:39 ` dpdklab
2024-07-10 16:49 ` dpdklab
2024-07-13 12:01 ` |SUCCESS| " dpdklab
2024-07-14 8:29 ` dpdklab
2024-07-14 15:09 ` dpdklab
2024-07-15 2:23 ` dpdklab
2024-07-15 2:37 ` 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=668d7db8.170a0220.19252.41dbSMTPIN_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).