automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw156851 [PATCH] rawdev: fix device ID retrieval function
Date: Tue, 23 Sep 2025 23:43:09 -0700 (PDT)	[thread overview]
Message-ID: <68d392fd.050a0220.ccc85.01eeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250924055654.1986682-1-nkishor@marvell.com>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/156851

_Performance Testing PASS_

Submitter: Nawal Kishor <nkishor@marvell.com>
Date: Wednesday, September 24 2025 05:56:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0e03ab647d07cd985a7cac36cefff5195cc3a07d

156851 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#245972

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.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.5%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.9%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -2.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34128/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-09-24  6:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250924055654.1986682-1-nkishor@marvell.com>
2025-09-24  5:23 ` |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function prototype qemudev
2025-09-24  5:28 ` qemudev
2025-09-24  5:55 ` checkpatch
2025-09-24  6:21 ` |PENDING| pw156851 [PATCH] rawdev: fix device ID retrieval function dpdklab
2025-09-24  6:22 ` dpdklab
2025-09-24  6:23 ` |SUCCESS| " dpdklab
2025-09-24  6:28 ` dpdklab
2025-09-24  6:31 ` |PENDING| " dpdklab
2025-09-24  6:41 ` |SUCCESS| " dpdklab
2025-09-24  6:43 ` dpdklab [this message]
2025-09-24  6:48 ` |PENDING| " dpdklab
2025-09-24  6:59 ` |WARNING| " dpdklab
2025-09-24  7:04 ` dpdklab
2025-09-24  7:09 ` |SUCCESS| " dpdklab
2025-09-24  7:12 ` dpdklab
2025-09-24  7:12 ` dpdklab
2025-09-24  7:19 ` dpdklab
2025-09-24  7:27 ` dpdklab
2025-09-24  7:39 ` dpdklab
2025-09-24  7:53 ` |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function prototype 0-day Robot
2025-09-24  7:53 ` 0-day Robot
2025-09-24  9:13 ` |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function dpdklab
2025-09-24  9:52 ` 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=68d392fd.050a0220.ccc85.01eeSMTPIN_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).