automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155564 [PATCH] [v2] dts: call hugepages configure at nod
Date: Mon, 28 Jul 2025 16:00:03 -0700 (PDT)	[thread overview]
Message-ID: <688800f3.050a0220.8c6bf.55f5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250728213209.1834486-1-probb@iol.unh.edu>

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/155564

_Performance Testing PASS_

Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Monday, July 28 2025 21:32:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4ca046f964fe358dc360c603f79f431beddfcab6

155564 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#238323

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.4%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-07-28 23:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250728213209.1834486-1-probb@iol.unh.edu>
2025-07-28 21:03 ` |SUCCESS| pw155564 [PATCH v2] dts: call hugepages configure at node setup qemudev
2025-07-28 21:08 ` qemudev
2025-07-28 21:37 ` checkpatch
2025-07-28 22:07 ` |SUCCESS| pw155564 [PATCH] [v2] dts: call hugepages configure at nod dpdklab
2025-07-28 22:18 ` dpdklab
2025-07-28 22:34 ` dpdklab
2025-07-28 22:43 ` |SUCCESS| pw155564 [PATCH v2] dts: call hugepages configure at node setup 0-day Robot
2025-07-28 22:43 ` |SUCCESS| pw155564 [PATCH] [v2] dts: call hugepages configure at nod dpdklab
2025-07-28 22:46 ` dpdklab
2025-07-28 22:46 ` dpdklab
2025-07-28 22:46 ` |PENDING| " dpdklab
2025-07-28 22:53 ` |SUCCESS| " dpdklab
2025-07-28 22:54 ` dpdklab
2025-07-28 22:54 ` dpdklab
2025-07-28 23:00 ` dpdklab [this message]
2025-07-28 23:14 ` dpdklab
2025-07-29  0:25 ` |PENDING| " dpdklab
2025-07-29  1:10 ` |SUCCESS| " dpdklab
2025-07-29  2:00 ` dpdklab
2025-07-29  2:10 ` dpdklab
2025-07-29  9: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=688800f3.050a0220.8c6bf.55f5SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).