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| pw152405-152411 [PATCH] [v2,7/7] dts: enable shell pooling
Date: Fri, 14 Mar 2025 09:49:49 -0700 (PDT) [thread overview]
Message-ID: <67d45e2d.050a0220.27310c.af6bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250314131857.1298247-8-luca.vizzarro@arm.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/152411
_Performance Testing PASS_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Friday, March 14 2025 13:18:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6d53332ee7a54a21e6ddbca4a4208e220fb9c860
152405-152411 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#217967
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | 0.6% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 1.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32831/
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:[~2025-03-14 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250314131857.1298247-8-luca.vizzarro@arm.com>
2025-03-14 13:20 ` |SUCCESS| pw152411 [PATCH v2 7/7] " checkpatch
2025-03-14 16:23 ` |SUCCESS| pw152405-152411 [PATCH] [v2,7/7] " dpdklab
2025-03-14 16:39 ` dpdklab
2025-03-14 16:44 ` dpdklab
2025-03-14 16:49 ` dpdklab [this message]
2025-03-14 16:51 ` dpdklab
2025-03-14 17:04 ` dpdklab
2025-03-14 17:10 ` dpdklab
2025-03-14 17:40 ` dpdklab
2025-03-14 17:50 ` dpdklab
2025-03-14 18:32 ` |PENDING| " dpdklab
2025-03-14 18:42 ` dpdklab
2025-03-14 19:42 ` |SUCCESS| " dpdklab
2025-03-14 20:26 ` dpdklab
2025-03-14 21:16 ` 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=67d45e2d.050a0220.27310c.af6bSMTPIN_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).