automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw154789-154796 [PATCH] [v7,8/8] lib/pmu: fix out-of-bound
Date: Fri, 27 Jun 2025 11:04:25 -0700 (PDT)	[thread overview]
Message-ID: <685edd29.050a0220.14b077.511cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250627154107.3405768-9-tduszynski@marvell.com>

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

_Performance Testing PASS_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Friday, June 27 2025 15:41:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2c6f1f0a847898732c18c8b37821850f1b48aa9d

154789-154796 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#233661

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: 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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | 2.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 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: 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.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%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-27 18:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250627154107.3405768-9-tduszynski@marvell.com>
2025-06-27 15:07 ` |SUCCESS| pw154789-154796 [PATCH v7 8/8] lib/pmu: fix out-of-bound access qemudev
2025-06-27 15:12 ` qemudev
2025-06-27 15:42 ` |SUCCESS| pw154796 " checkpatch
2025-06-27 17:23 ` 0-day Robot
2025-06-27 17:41 ` |SUCCESS| pw154789-154796 [PATCH] [v7,8/8] lib/pmu: fix out-of-bound dpdklab
2025-06-27 18:04 ` dpdklab [this message]
2025-06-27 19:10 ` dpdklab
2025-06-27 19:11 ` |PENDING| " dpdklab
2025-06-27 19:25 ` |SUCCESS| " dpdklab
2025-06-27 20:00 ` dpdklab
2025-06-27 20:39 ` |PENDING| " dpdklab
2025-06-27 21:31 ` |SUCCESS| " dpdklab
2025-06-27 22:08 ` dpdklab
2025-06-27 22:22 ` dpdklab
2025-06-27 22:57 ` dpdklab
2025-06-27 22:57 ` dpdklab
2025-06-27 22:58 ` dpdklab
2025-06-27 23:09 ` |WARNING| " dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` 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=685edd29.050a0220.14b077.511cSMTPIN_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).