From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 39a8b1251b204d3898b4c462184f60bda1b64698
Date: Fri, 12 Jan 2024 23:41:09 -0800 (PST) [thread overview]
Message-ID: <65a23e95.170a0220.1cfe5.7da3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net
39a8b1251b204d3898b4c462184f60bda1b64698 --> 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.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27656/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-13 7:41 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 7:41 dpdklab [this message]
2024-01-13 7:41 dpdklab
2024-01-13 7:42 dpdklab
2024-01-13 7:42 dpdklab
2024-01-13 7:43 dpdklab
2024-01-13 7:43 dpdklab
2024-01-13 7:44 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:45 dpdklab
2024-01-13 7:46 dpdklab
2024-01-13 7:46 dpdklab
2024-01-13 7:46 dpdklab
2024-01-13 7:46 dpdklab
2024-01-13 7:46 dpdklab
2024-01-13 7:47 dpdklab
2024-01-13 7:47 dpdklab
2024-01-13 7:47 dpdklab
2024-01-13 7:47 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:48 dpdklab
2024-01-13 7:49 dpdklab
2024-01-13 7:49 dpdklab
2024-01-13 7:50 dpdklab
2024-01-13 7:50 dpdklab
2024-01-13 7:50 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:51 dpdklab
2024-01-13 7:55 dpdklab
2024-01-13 7:55 dpdklab
2024-01-13 7:56 dpdklab
2024-01-13 7:57 dpdklab
2024-01-13 8:02 dpdklab
2024-01-13 8:03 dpdklab
2024-01-13 8:04 dpdklab
2024-01-13 8:07 dpdklab
2024-01-13 8:08 dpdklab
2024-01-13 8:08 dpdklab
2024-01-13 8:10 dpdklab
2024-01-13 8:10 dpdklab
2024-01-13 8:13 dpdklab
2024-01-13 8:14 dpdklab
2024-01-13 8:56 dpdklab
2024-01-13 9:08 dpdklab
2024-01-13 9:43 dpdklab
2024-01-13 23:24 dpdklab
2024-01-13 23:31 dpdklab
2024-01-17 9:06 dpdklab
2024-01-18 17:03 dpdklab
2024-01-18 17:08 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:15 dpdklab
2024-01-18 17:20 dpdklab
2024-01-18 17:20 dpdklab
2024-01-18 17:24 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:42 dpdklab
2024-01-18 17:45 dpdklab
2024-01-18 18:07 dpdklab
2024-01-18 18:17 dpdklab
2024-01-18 18:17 dpdklab
2024-01-18 18:21 dpdklab
2024-01-18 18:23 dpdklab
2024-01-18 18:25 dpdklab
2024-01-18 18:26 dpdklab
2024-01-18 18:27 dpdklab
2024-01-18 18:29 dpdklab
2024-01-18 18:29 dpdklab
2024-01-18 18:30 dpdklab
2024-01-18 18:34 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:38 dpdklab
2024-01-18 18:40 dpdklab
2024-01-18 18:40 dpdklab
2024-01-18 18:42 dpdklab
2024-01-18 18:42 dpdklab
2024-01-18 18:42 dpdklab
2024-01-18 18:43 dpdklab
2024-01-18 18:43 dpdklab
2024-01-18 18:43 dpdklab
2024-01-18 18:46 dpdklab
2024-01-18 18:46 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:49 dpdklab
2024-01-18 18:49 dpdklab
2024-01-18 18:53 dpdklab
2024-01-18 19:06 dpdklab
2024-01-18 19:15 dpdklab
2024-01-18 19:25 dpdklab
2024-01-18 19:54 dpdklab
2024-01-18 23:30 dpdklab
2024-01-18 23:53 dpdklab
2024-01-19 2:32 dpdklab
2024-01-19 22:15 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=65a23e95.170a0220.1cfe5.7da3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).