From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 34c0c38ab772e8eea5243f530866d5b68519e7c7
Date: Fri, 03 Nov 2023 19:15:35 -0700 (PDT) [thread overview]
Message-ID: <6545a947.920a0220.4b61c.7488SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk
34c0c38ab772e8eea5243f530866d5b68519e7c7 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26826/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-04 2:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 2:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 9:42 dpdklab
2023-11-04 3:32 dpdklab
2023-11-04 3:26 dpdklab
2023-11-04 3:23 dpdklab
2023-11-04 3:00 dpdklab
2023-11-04 2:50 dpdklab
2023-11-04 2:30 dpdklab
2023-11-04 2:30 dpdklab
2023-11-04 2:27 dpdklab
2023-11-04 2:27 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:26 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:25 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:24 dpdklab
2023-11-04 2:23 dpdklab
2023-11-04 2:23 dpdklab
2023-11-04 2:23 dpdklab
2023-11-04 2:22 dpdklab
2023-11-04 2:22 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:21 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:20 dpdklab
2023-11-04 2:19 dpdklab
2023-11-04 2:19 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:18 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:17 dpdklab
2023-11-04 2:15 dpdklab
2023-11-04 2:14 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:13 dpdklab
2023-11-04 2:10 dpdklab
2023-11-04 2:10 dpdklab
2023-11-04 1:54 dpdklab
2023-11-04 1:49 dpdklab
2023-11-04 1:39 dpdklab
2023-11-04 1:39 dpdklab
2023-11-04 1: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=6545a947.920a0220.4b61c.7488SMTPIN_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).