From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142513-142516 [PATCH] [4/4] test: run timer secondary te
Date: Fri, 19 Jul 2024 03:39:25 -0700 (PDT) [thread overview]
Message-ID: <669a425d.050a0220.1a918.2b7aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240718191049.84865-5-stephen@networkplumber.org>
Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/142516
_Performance Testing pending_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, July 18 2024 19:07:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142513-142516 --> performance testing pending
Upstream job id: Template-DTS-Pipeline#169039
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 1.6% |
+------------+---------+----------+-------------+------------------------------+
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/30558/
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-19 10:39 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240718191049.84865-5-stephen@networkplumber.org>
2024-07-18 19:01 ` |SUCCESS| pw142513-142516 [PATCH 4/4] test: run timer secondary tests as part of fast suite qemudev
2024-07-18 19:06 ` qemudev
2024-07-18 19:12 ` |SUCCESS| pw142516 " checkpatch
2024-07-18 20:03 ` |FAILURE| " 0-day Robot
2024-07-19 8:55 ` |PENDING| pw142513-142516 [PATCH] [4/4] test: run timer secondary te dpdklab
2024-07-19 9:03 ` |SUCCESS| " dpdklab
2024-07-19 9:04 ` dpdklab
2024-07-19 9:06 ` dpdklab
2024-07-19 9:17 ` dpdklab
2024-07-19 9:18 ` dpdklab
2024-07-19 9:20 ` dpdklab
2024-07-19 9:20 ` dpdklab
2024-07-19 9:38 ` dpdklab
2024-07-19 10:39 ` dpdklab [this message]
2024-07-19 10:47 ` dpdklab
2024-07-19 10:56 ` |PENDING| " dpdklab
2024-07-19 10:58 ` dpdklab
2024-07-19 11:04 ` dpdklab
2024-07-19 11:06 ` dpdklab
2024-07-19 11:11 ` dpdklab
2024-07-19 11:13 ` dpdklab
2024-07-19 11:16 ` dpdklab
2024-07-19 11:18 ` dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:23 ` |SUCCESS| " dpdklab
2024-07-19 11:25 ` |PENDING| " dpdklab
2024-07-19 11:25 ` dpdklab
2024-07-19 11:26 ` dpdklab
2024-07-19 11:26 ` |SUCCESS| " dpdklab
2024-07-19 11:26 ` |PENDING| " dpdklab
2024-07-19 11:27 ` dpdklab
2024-07-19 11:30 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:33 ` dpdklab
2024-07-19 11:34 ` |FAILURE| " dpdklab
2024-07-19 11:35 ` dpdklab
2024-07-19 11:35 ` |PENDING| " dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:38 ` dpdklab
2024-07-19 11:38 ` dpdklab
2024-07-19 11:42 ` dpdklab
2024-07-19 11:43 ` dpdklab
2024-07-19 11:44 ` dpdklab
2024-07-19 11:44 ` dpdklab
2024-07-19 11:46 ` dpdklab
2024-07-19 11:53 ` dpdklab
2024-07-19 11:57 ` |SUCCESS| " dpdklab
2024-07-19 12:00 ` |PENDING| " dpdklab
2024-07-19 12:00 ` dpdklab
2024-07-19 12:02 ` dpdklab
2024-07-19 12:02 ` dpdklab
2024-07-19 12:03 ` dpdklab
2024-07-19 12:04 ` dpdklab
2024-07-19 12:08 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:10 ` dpdklab
2024-07-19 12:10 ` dpdklab
2024-07-19 12:12 ` |FAILURE| " dpdklab
2024-07-19 12:12 ` |PENDING| " dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:15 ` |SUCCESS| " dpdklab
2024-07-19 12:15 ` |PENDING| " dpdklab
2024-07-19 12:16 ` |FAILURE| " dpdklab
2024-07-19 12:18 ` |SUCCESS| " dpdklab
2024-07-19 12:21 ` |FAILURE| " dpdklab
2024-07-19 12:22 ` dpdklab
2024-07-19 12:23 ` |SUCCESS| " dpdklab
2024-07-19 12:24 ` |FAILURE| " dpdklab
2024-07-19 12:27 ` dpdklab
2024-07-19 12:28 ` dpdklab
2024-07-19 12:28 ` |SUCCESS| " dpdklab
2024-07-19 12:28 ` |PENDING| " dpdklab
2024-07-19 12:28 ` |FAILURE| " dpdklab
2024-07-19 12:33 ` dpdklab
2024-07-19 12:33 ` |SUCCESS| " dpdklab
2024-07-19 12:34 ` |FAILURE| " dpdklab
2024-07-19 12:37 ` dpdklab
2024-07-19 12:38 ` dpdklab
2024-07-19 12:40 ` dpdklab
2024-07-19 12:40 ` dpdklab
2024-07-19 12:41 ` dpdklab
2024-07-19 12:43 ` dpdklab
2024-07-19 12:50 ` |PENDING| " dpdklab
2024-07-19 12:52 ` |SUCCESS| " dpdklab
2024-07-19 12:55 ` |PENDING| " dpdklab
2024-07-19 12:56 ` dpdklab
2024-07-19 12:57 ` dpdklab
2024-07-19 12:59 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:03 ` dpdklab
2024-07-19 13:05 ` dpdklab
2024-07-19 13:06 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:11 ` dpdklab
2024-07-19 13:12 ` dpdklab
2024-07-19 13:12 ` dpdklab
2024-07-19 13:15 ` dpdklab
2024-07-19 13:15 ` dpdklab
2024-07-19 13:19 ` |SUCCESS| " dpdklab
2024-07-19 13:22 ` |PENDING| " dpdklab
2024-07-19 13:30 ` dpdklab
2024-07-19 13:31 ` |FAILURE| " dpdklab
2024-07-19 13:48 ` |SUCCESS| " dpdklab
2024-07-19 20:24 ` 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=669a425d.050a0220.1a918.2b7aSMTPIN_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).