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] 57c348072cbe0874c552b4c7745fbf37f96c8eb2
Date: Tue, 21 Nov 2023 11:45:49 -0800 (PST) [thread overview]
Message-ID: <655d08ed.920a0220.d98f.a239SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net
57c348072cbe0874c552b4c7745fbf37f96c8eb2 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27068/
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-21 19:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 19:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 20:48 dpdklab
2023-11-21 20:10 dpdklab
2023-11-21 20:03 dpdklab
2023-11-21 20:00 dpdklab
2023-11-21 19:59 dpdklab
2023-11-21 19:58 dpdklab
2023-11-21 19:55 dpdklab
2023-11-21 19:51 dpdklab
2023-11-21 19:51 dpdklab
2023-11-21 19:51 dpdklab
2023-11-21 19:49 dpdklab
2023-11-21 19:49 dpdklab
2023-11-21 19:49 dpdklab
2023-11-21 19:49 dpdklab
2023-11-21 19:46 dpdklab
2023-11-21 19:45 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:43 dpdklab
2023-11-21 19:41 dpdklab
2023-11-21 19:41 dpdklab
2023-11-21 19:41 dpdklab
2023-11-21 19:41 dpdklab
2023-11-21 19:40 dpdklab
2023-11-21 19:40 dpdklab
2023-11-21 19:40 dpdklab
2023-11-21 19:40 dpdklab
2023-11-21 19:35 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=655d08ed.920a0220.d98f.a239SMTPIN_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).