From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 080211fd1a956bd27a74ddc377db73c8741cf40f
Date: Mon, 04 Mar 2024 04:38:40 -0800 (PST) [thread overview]
Message-ID: <65e5c0d0.050a0220.6902d.0aa4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net-intel
080211fd1a956bd27a74ddc377db73c8741cf40f --> performance testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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 | 1.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28298/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-04 12:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 12:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-08 3:20 dpdklab
2024-03-08 2:47 dpdklab
2024-03-08 2:15 dpdklab
2024-03-04 15:49 dpdklab
2024-03-04 14:27 dpdklab
2024-03-04 14:04 dpdklab
2024-03-04 13:56 dpdklab
2024-03-04 13:34 dpdklab
2024-03-04 13:32 dpdklab
2024-03-04 13:28 dpdklab
2024-03-04 13:27 dpdklab
2024-03-04 13:27 dpdklab
2024-03-04 13:26 dpdklab
2024-03-04 13:26 dpdklab
2024-03-04 13:26 dpdklab
2024-03-04 13:26 dpdklab
2024-03-04 13:25 dpdklab
2024-03-04 13:19 dpdklab
2024-03-04 13:18 dpdklab
2024-03-04 13:18 dpdklab
2024-03-04 13:07 dpdklab
2024-03-04 13:07 dpdklab
2024-03-04 13:07 dpdklab
2024-03-04 13:06 dpdklab
2024-03-04 13:06 dpdklab
2024-03-04 13:06 dpdklab
2024-03-04 13:05 dpdklab
2024-03-04 13:05 dpdklab
2024-03-04 13:05 dpdklab
2024-03-04 13:05 dpdklab
2024-03-04 13:05 dpdklab
2024-03-04 13:03 dpdklab
2024-03-04 13:02 dpdklab
2024-03-04 13:00 dpdklab
2024-03-04 13:00 dpdklab
2024-03-04 12:59 dpdklab
2024-03-04 12:59 dpdklab
2024-03-04 12:59 dpdklab
2024-03-04 12:58 dpdklab
2024-03-04 12:58 dpdklab
2024-03-04 12:58 dpdklab
2024-03-04 12:57 dpdklab
2024-03-04 12:56 dpdklab
2024-03-04 12:56 dpdklab
2024-03-04 12:56 dpdklab
2024-03-04 12:56 dpdklab
2024-03-04 12:56 dpdklab
2024-03-04 12:55 dpdklab
2024-03-04 12:55 dpdklab
2024-03-04 12:55 dpdklab
2024-03-04 12:55 dpdklab
2024-03-04 12:51 dpdklab
2024-03-04 12:51 dpdklab
2024-03-04 12:51 dpdklab
2024-03-04 12:40 dpdklab
2024-03-04 12:40 dpdklab
2024-03-04 12:37 dpdklab
2024-03-04 12:37 dpdklab
2024-03-04 12:37 dpdklab
2024-03-04 12:26 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=65e5c0d0.050a0220.6902d.0aa4SMTPIN_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).