From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139559 [PATCH] net/ionic: clean up logging issues
Date: Fri, 19 Apr 2024 18:04:43 -0700 (PDT) [thread overview]
Message-ID: <662314ab.a70a0220.e36f6.19b3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240419202556.46188-1-andrew.boyer@amd.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/139559
_Performance Testing PASS_
Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Friday, April 19 2024 20:25:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7b668b7d65ba33783c280d08489fa31685bd0ee6
139559 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29832/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-20 1:04 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419202556.46188-1-andrew.boyer@amd.com>
2024-04-19 20:27 ` checkpatch
2024-04-20 0:33 ` dpdklab
2024-04-20 0:34 ` dpdklab
2024-04-20 0:34 ` dpdklab
2024-04-20 0:34 ` dpdklab
2024-04-20 0:35 ` dpdklab
2024-04-20 0:52 ` dpdklab
2024-04-20 1:01 ` dpdklab
2024-04-20 1:03 ` dpdklab
2024-04-20 1:03 ` dpdklab
2024-04-20 1:04 ` dpdklab
2024-04-20 1:04 ` dpdklab [this message]
2024-04-20 1:04 ` dpdklab
2024-04-20 1:05 ` dpdklab
2024-04-20 1:05 ` dpdklab
2024-04-20 1:05 ` dpdklab
2024-04-20 1:05 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:06 ` dpdklab
2024-04-20 1:07 ` dpdklab
2024-04-20 1:08 ` dpdklab
2024-04-20 1:08 ` dpdklab
2024-04-20 1:08 ` dpdklab
2024-04-20 1:08 ` dpdklab
2024-04-20 1:09 ` dpdklab
2024-04-20 1:09 ` dpdklab
2024-04-20 1:09 ` dpdklab
2024-04-20 1:09 ` dpdklab
2024-04-20 1:10 ` dpdklab
2024-04-20 1:10 ` dpdklab
2024-04-20 1:10 ` dpdklab
2024-04-20 1:11 ` dpdklab
2024-04-20 1:11 ` dpdklab
2024-04-20 1:11 ` dpdklab
2024-04-20 1:11 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:12 ` dpdklab
2024-04-20 1:13 ` dpdklab
2024-04-20 1:13 ` dpdklab
2024-04-20 1:13 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:20 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:21 ` dpdklab
2024-04-20 1:22 ` dpdklab
2024-04-20 1:22 ` dpdklab
2024-04-20 1:22 ` dpdklab
2024-04-20 1:31 ` dpdklab
2024-04-20 1:31 ` dpdklab
2024-04-20 1:32 ` dpdklab
2024-04-20 1:32 ` dpdklab
2024-04-20 1:33 ` dpdklab
2024-04-20 1:33 ` dpdklab
2024-04-20 1:33 ` dpdklab
2024-04-20 1:34 ` dpdklab
2024-04-20 1:35 ` dpdklab
2024-04-20 1:35 ` dpdklab
2024-04-20 1:36 ` dpdklab
2024-04-20 1:41 ` dpdklab
2024-04-20 1:47 ` dpdklab
2024-04-20 1:51 ` dpdklab
2024-04-20 1:52 ` dpdklab
2024-04-20 2:12 ` dpdklab
2024-04-20 2:12 ` dpdklab
2024-04-20 2:26 ` dpdklab
2024-04-20 2:31 ` dpdklab
2024-04-22 2:00 ` qemudev
2024-04-22 2:05 ` qemudev
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=662314ab.a70a0220.e36f6.19b3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).