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] 7382242eff69555396d0145b5efee68646e81120
Date: Fri, 12 May 2023 20:43:14 -0700 (PDT) [thread overview]
Message-ID: <645f0752.050a0220.b3ae3.48c8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net
7382242eff69555396d0145b5efee68646e81120 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 128 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 512 | 64 | 0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 128 | 64 | 0.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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.8% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24545/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-13 3:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 3:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-13 4:05 dpdklab
2023-05-13 4:00 dpdklab
2023-05-13 3:56 dpdklab
2023-05-13 3:47 dpdklab
2023-05-12 21:55 dpdklab
2023-05-12 21:54 dpdklab
2023-05-12 21:08 dpdklab
2023-05-12 20:31 dpdklab
2023-05-12 20:10 dpdklab
2023-05-12 19:38 dpdklab
2023-05-12 19:17 dpdklab
2023-05-12 19:05 dpdklab
2023-05-12 18:54 dpdklab
2023-05-12 18:42 dpdklab
2023-05-12 18:40 dpdklab
2023-05-12 18:39 dpdklab
2023-05-12 18:34 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=645f0752.050a0220.b3ae3.48c8SMTPIN_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).