From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154514-154517 [PATCH] [v5,4/4] doc: announce TxPP suppor
Date: Tue, 17 Jun 2025 03:10:52 -0700 (PDT) [thread overview]
Message-ID: <68513f2c.170a0220.3c30ac.7073SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250617001429.551262-5-soumyadeep.hore@intel.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/154517
_Performance Testing PASS_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Tuesday, June 17 2025 00:14:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dbeb8ae8d09387bd525353f4a5aa6ec152cddffa
154514-154517 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#231248
Test environment and result as below:
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33432/
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-06-17 10:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250617001429.551262-5-soumyadeep.hore@intel.com>
2025-06-17 7:57 ` |SUCCESS| pw154514-154517 [PATCH v5 4/4] doc: announce TxPP support for E830 adapters qemudev
2025-06-17 8:01 ` qemudev
2025-06-17 8:24 ` |SUCCESS| pw154517 " checkpatch
2025-06-17 10:10 ` dpdklab [this message]
2025-06-17 10:11 ` |SUCCESS| pw154514-154517 [PATCH] [v5,4/4] doc: announce TxPP suppor dpdklab
2025-06-17 10:13 ` dpdklab
2025-06-17 10:22 ` dpdklab
2025-06-17 10:33 ` |PENDING| " dpdklab
2025-06-17 10:36 ` |FAILURE| " dpdklab
2025-06-17 10:40 ` |SUCCESS| " dpdklab
2025-06-17 10:45 ` |PENDING| " dpdklab
2025-06-17 10:49 ` |FAILURE| " dpdklab
2025-06-17 10:50 ` |PENDING| " dpdklab
2025-06-17 11:14 ` |SUCCESS| " dpdklab
2025-06-17 11:14 ` |FAILURE| " dpdklab
2025-06-17 11:18 ` |SUCCESS| " dpdklab
2025-06-17 11:23 ` dpdklab
2025-06-17 13:09 ` dpdklab
2025-06-17 13:20 ` dpdklab
2025-06-17 13:26 ` dpdklab
2025-06-17 16:37 ` |PENDING| " dpdklab
2025-06-17 17:02 ` |SUCCESS| " 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=68513f2c.170a0220.3c30ac.7073SMTPIN_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).