From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 68453e54f42c392520a9cbf5c3be4198272ca507
Date: Thu, 02 Nov 2023 10:55:32 -0700 (PDT) [thread overview]
Message-ID: <6543e294.a70a0220.b7a90.04deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-virtio
68453e54f42c392520a9cbf5c3be4198272ca507 --> 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26792/
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-02 17:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 2:12 dpdklab
2023-11-02 20:16 dpdklab
2023-11-02 19:54 dpdklab
2023-11-02 19:26 dpdklab
2023-11-02 19:19 dpdklab
2023-11-02 19:11 dpdklab
2023-11-02 19:10 dpdklab
2023-11-02 19:09 dpdklab
2023-11-02 19:03 dpdklab
2023-11-02 19:03 dpdklab
2023-11-02 19:01 dpdklab
2023-11-02 18:59 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:54 dpdklab
2023-11-02 18:54 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:52 dpdklab
2023-11-02 18:39 dpdklab
2023-11-02 18:38 dpdklab
2023-11-02 18:33 dpdklab
2023-11-02 18:23 dpdklab
2023-11-02 18:07 dpdklab
2023-11-02 18:02 dpdklab
2023-11-02 17:59 dpdklab
2023-11-02 17:35 dpdklab
2023-11-02 17:31 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=6543e294.a70a0220.b7a90.04deSMTPIN_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).