From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] a34fc20b7950855129da4a8ad7724180039acb0a
Date: Fri, 19 Jul 2024 13:37:32 -0700 (PDT) [thread overview]
Message-ID: <669ace8c.170a0220.3a7c19.15ecSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing pending_
Branch: dpdk-next-crypto
a34fc20b7950855129da4a8ad7724180039acb0a --> performance testing pending
Upstream job id: Template-DTS-Pipeline#169185
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
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
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/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/tarballs/29920/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-19 20:37 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 20:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 21:54 dpdklab
2024-07-19 21:40 dpdklab
2024-07-19 21:30 dpdklab
2024-07-19 21:29 dpdklab
2024-07-19 21:29 dpdklab
2024-07-19 21:24 dpdklab
2024-07-19 21:23 dpdklab
2024-07-19 21:23 dpdklab
2024-07-19 21:20 dpdklab
2024-07-19 21:18 dpdklab
2024-07-19 21:18 dpdklab
2024-07-19 21:18 dpdklab
2024-07-19 21:18 dpdklab
2024-07-19 21:17 dpdklab
2024-07-19 21:16 dpdklab
2024-07-19 21:15 dpdklab
2024-07-19 21:12 dpdklab
2024-07-19 21:12 dpdklab
2024-07-19 21:12 dpdklab
2024-07-19 21:11 dpdklab
2024-07-19 21:11 dpdklab
2024-07-19 21:11 dpdklab
2024-07-19 21:11 dpdklab
2024-07-19 21:10 dpdklab
2024-07-19 21:08 dpdklab
2024-07-19 21:07 dpdklab
2024-07-19 21:06 dpdklab
2024-07-19 21:04 dpdklab
2024-07-19 21:04 dpdklab
2024-07-19 21:03 dpdklab
2024-07-19 21:03 dpdklab
2024-07-19 21:02 dpdklab
2024-07-19 21:02 dpdklab
2024-07-19 20:59 dpdklab
2024-07-19 20:59 dpdklab
2024-07-19 20:58 dpdklab
2024-07-19 20:57 dpdklab
2024-07-19 20:57 dpdklab
2024-07-19 20:57 dpdklab
2024-07-19 20:57 dpdklab
2024-07-19 20:56 dpdklab
2024-07-19 20:54 dpdklab
2024-07-19 20:53 dpdklab
2024-07-19 20:53 dpdklab
2024-07-19 20:52 dpdklab
2024-07-19 20:51 dpdklab
2024-07-19 20:50 dpdklab
2024-07-19 20:49 dpdklab
2024-07-19 20:47 dpdklab
2024-07-19 20:46 dpdklab
2024-07-19 20:45 dpdklab
2024-07-19 20:45 dpdklab
2024-07-19 20:44 dpdklab
2024-07-19 20:44 dpdklab
2024-07-19 20:44 dpdklab
2024-07-19 20:44 dpdklab
2024-07-19 20:43 dpdklab
2024-07-19 20:42 dpdklab
2024-07-19 20:41 dpdklab
2024-07-19 20:40 dpdklab
2024-07-19 20:39 dpdklab
2024-07-19 20:38 dpdklab
2024-07-19 20:37 dpdklab
2024-07-19 20:36 dpdklab
2024-07-19 20:34 dpdklab
2024-07-19 20:33 dpdklab
2024-07-19 20:33 dpdklab
2024-07-19 20:31 dpdklab
2024-07-19 20:31 dpdklab
2024-07-19 20:28 dpdklab
2024-07-19 20:27 dpdklab
2024-07-19 20:13 dpdklab
2024-07-19 20:06 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=669ace8c.170a0220.3a7c19.15ecSMTPIN_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).