From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, 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] 3410f4d514ad8970b30dde9d3f6ad6105bcbd650
Date: Wed, 20 Sep 2023 11:49:42 -0700 (PDT) [thread overview]
Message-ID: <650b3ec6.4a0a0220.8dc4d.7fecSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net
3410f4d514ad8970b30dde9d3f6ad6105bcbd650 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26186/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-20 18:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 18:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 19:04 dpdklab
2023-09-21 19:02 dpdklab
2023-09-21 18:58 dpdklab
2023-09-21 18:49 dpdklab
2023-09-20 23:07 dpdklab
2023-09-20 22:34 dpdklab
2023-09-20 22:27 dpdklab
2023-09-20 22:26 dpdklab
2023-09-20 22:20 dpdklab
2023-09-20 22:13 dpdklab
2023-09-20 22:12 dpdklab
2023-09-20 22:04 dpdklab
2023-09-20 22:04 dpdklab
2023-09-20 21:54 dpdklab
2023-09-20 21:53 dpdklab
2023-09-20 21:05 dpdklab
2023-09-20 20:42 dpdklab
2023-09-20 20:38 dpdklab
2023-09-20 20:36 dpdklab
2023-09-20 20:34 dpdklab
2023-09-20 20:17 dpdklab
2023-09-20 20:12 dpdklab
2023-09-20 20:06 dpdklab
2023-09-20 20:05 dpdklab
2023-09-20 20:03 dpdklab
2023-09-20 19:59 dpdklab
2023-09-20 19:56 dpdklab
2023-09-20 19:54 dpdklab
2023-09-20 19:52 dpdklab
2023-09-20 19:49 dpdklab
2023-09-20 19:48 dpdklab
2023-09-20 19:46 dpdklab
2023-09-20 19:42 dpdklab
2023-09-20 19:40 dpdklab
2023-09-20 19:37 dpdklab
2023-09-20 19:36 dpdklab
2023-09-20 19:34 dpdklab
2023-09-20 19:31 dpdklab
2023-09-20 19:29 dpdklab
2023-09-20 19:15 dpdklab
2023-09-20 19:07 dpdklab
2023-09-20 18:57 dpdklab
2023-09-20 18:52 dpdklab
2023-09-20 18:47 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=650b3ec6.4a0a0220.8dc4d.7fecSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).