From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw143005-143006 [PATCH] [v9,2/2] dts: initial queue start/
Date: Thu, 08 Aug 2024 02:48:23 -0700 (PDT) [thread overview]
Message-ID: <66b49467.050a0220.b266.1514SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240807193611.23060-3-dmarx@iol.unh.edu>
Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/143006
_Performance Testing pending_
Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Wednesday, August 07 2024 19:36:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
143005-143006 --> performance testing pending
Upstream job id: Template-DTS-Pipeline#173699
Test environment and result as below:
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
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -1.8% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30741/
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-08-08 9:48 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240807193611.23060-3-dmarx@iol.unh.edu>
2024-08-07 19:30 ` |SUCCESS| pw143005-143006 [PATCH v9 2/2] dts: initial queue start/stop suite implementation qemudev
2024-08-07 19:35 ` qemudev
2024-08-07 19:36 ` |SUCCESS| pw143006 " checkpatch
2024-08-07 20:23 ` 0-day Robot
2024-08-08 6:17 ` |SUCCESS| pw143005-143006 [PATCH] [v9,2/2] dts: initial queue start/ dpdklab
2024-08-08 7:15 ` |PENDING| " dpdklab
2024-08-08 7:28 ` |SUCCESS| " dpdklab
2024-08-08 7:29 ` |PENDING| " dpdklab
2024-08-08 7:38 ` |SUCCESS| " dpdklab
2024-08-08 7:39 ` dpdklab
2024-08-08 7:52 ` dpdklab
2024-08-08 7:52 ` dpdklab
2024-08-08 8:01 ` |PENDING| " dpdklab
2024-08-08 8:04 ` dpdklab
2024-08-08 8:07 ` dpdklab
2024-08-08 8:14 ` dpdklab
2024-08-08 8:18 ` dpdklab
2024-08-08 8:18 ` dpdklab
2024-08-08 8:19 ` dpdklab
2024-08-08 8:26 ` dpdklab
2024-08-08 8:26 ` dpdklab
2024-08-08 8:30 ` dpdklab
2024-08-08 8:31 ` dpdklab
2024-08-08 8:33 ` dpdklab
2024-08-08 8:36 ` dpdklab
2024-08-08 8:38 ` dpdklab
2024-08-08 8:44 ` |SUCCESS| " dpdklab
2024-08-08 8:46 ` |PENDING| " dpdklab
2024-08-08 8:57 ` dpdklab
2024-08-08 9:00 ` dpdklab
2024-08-08 9:01 ` dpdklab
2024-08-08 9:01 ` dpdklab
2024-08-08 9:03 ` dpdklab
2024-08-08 9:06 ` |SUCCESS| " dpdklab
2024-08-08 9:06 ` |PENDING| " dpdklab
2024-08-08 9:06 ` dpdklab
2024-08-08 9:07 ` dpdklab
2024-08-08 9:08 ` |SUCCESS| " dpdklab
2024-08-08 9:10 ` |PENDING| " dpdklab
2024-08-08 9:13 ` dpdklab
2024-08-08 9:15 ` dpdklab
2024-08-08 9:15 ` dpdklab
2024-08-08 9:16 ` dpdklab
2024-08-08 9:22 ` dpdklab
2024-08-08 9:22 ` dpdklab
2024-08-08 9:28 ` dpdklab
2024-08-08 9:36 ` dpdklab
2024-08-08 9:41 ` dpdklab
2024-08-08 9:43 ` dpdklab
2024-08-08 9:43 ` dpdklab
2024-08-08 9:45 ` dpdklab
2024-08-08 9:48 ` dpdklab [this message]
2024-08-08 9:49 ` dpdklab
2024-08-08 9:51 ` dpdklab
2024-08-08 9:56 ` |SUCCESS| " dpdklab
2024-08-08 9:57 ` dpdklab
2024-08-08 10:32 ` dpdklab
2024-08-08 11:04 ` |PENDING| " dpdklab
2024-08-08 11:06 ` dpdklab
2024-08-08 11:08 ` dpdklab
2024-08-08 11:10 ` dpdklab
2024-08-08 11:11 ` dpdklab
2024-08-08 11:12 ` dpdklab
2024-08-08 11:13 ` dpdklab
2024-08-08 11:14 ` dpdklab
2024-08-08 11:14 ` dpdklab
2024-08-08 11:14 ` dpdklab
2024-08-08 11:15 ` dpdklab
2024-08-08 11:16 ` dpdklab
2024-08-08 11:17 ` dpdklab
2024-08-08 11:18 ` dpdklab
2024-08-08 11:18 ` dpdklab
2024-08-08 11:18 ` dpdklab
2024-08-08 11:18 ` dpdklab
2024-08-08 11:19 ` dpdklab
2024-08-08 11:21 ` dpdklab
2024-08-08 11:21 ` dpdklab
2024-08-08 11:24 ` |SUCCESS| " dpdklab
2024-08-08 11:27 ` |PENDING| " dpdklab
2024-08-08 11:27 ` dpdklab
2024-08-08 11:27 ` dpdklab
2024-08-08 11:29 ` dpdklab
2024-08-08 11:30 ` dpdklab
2024-08-08 11:32 ` |SUCCESS| " dpdklab
2024-08-08 11:32 ` |PENDING| " dpdklab
2024-08-08 11:33 ` dpdklab
2024-08-08 11:33 ` dpdklab
2024-08-08 11:34 ` dpdklab
2024-08-08 11:34 ` dpdklab
2024-08-08 11:36 ` |SUCCESS| " dpdklab
2024-08-08 11:38 ` |PENDING| " dpdklab
2024-08-08 11:38 ` dpdklab
2024-08-08 11:40 ` dpdklab
2024-08-08 11:40 ` dpdklab
2024-08-08 11:41 ` dpdklab
2024-08-08 11:41 ` dpdklab
2024-08-08 11:42 ` dpdklab
2024-08-08 11:43 ` |SUCCESS| " dpdklab
2024-08-08 11:44 ` |PENDING| " dpdklab
2024-08-08 11:47 ` dpdklab
2024-08-08 11:47 ` dpdklab
2024-08-08 11:48 ` dpdklab
2024-08-08 11:48 ` |SUCCESS| " dpdklab
2024-08-08 11:49 ` |PENDING| " dpdklab
2024-08-08 11:51 ` dpdklab
2024-08-08 11:53 ` dpdklab
2024-08-08 11:53 ` |SUCCESS| " dpdklab
2024-08-08 12:01 ` dpdklab
2024-08-08 12:05 ` |PENDING| " dpdklab
2024-08-08 12:07 ` |SUCCESS| " dpdklab
2024-08-08 12:17 ` |PENDING| " dpdklab
2024-08-08 12:18 ` dpdklab
2024-08-08 12:33 ` |SUCCESS| " dpdklab
2024-08-08 14:12 ` 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=66b49467.050a0220.b266.1514SMTPIN_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).