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| pw159050 [PATCH] [v2] devtools: check patch from stdin onl
Date: Fri, 28 Nov 2025 12:19:05 -0800 (PST)	[thread overview]
Message-ID: <692a03b9.170a0220.91139.8da9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251128144127.1552516-1-thomas@monjalon.net>

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

_Performance Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Friday, November 28 2025 14:40:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4695b3e82a26e6a81b1b96175431469ac2b01d0

159050 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#256767

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-11-28 20:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251128144127.1552516-1-thomas@monjalon.net>
2025-11-28 14:07 ` |SUCCESS| pw159050 [PATCH v2] devtools: check patch from stdin only if nothing else qemudev
2025-11-28 14:12 ` qemudev
2025-11-28 14:41 ` checkpatch
2025-11-28 16:21 ` 0-day Robot
2025-11-28 16:21 ` 0-day Robot
2025-11-28 19:41 ` |PENDING| pw159050 [PATCH] [v2] devtools: check patch from stdin onl dpdklab
2025-11-28 19:41 ` dpdklab
2025-11-28 19:50 ` |SUCCESS| " dpdklab
2025-11-28 19:51 ` |PENDING| " dpdklab
2025-11-28 19:54 ` |SUCCESS| " dpdklab
2025-11-28 20:04 ` dpdklab
2025-11-28 20:05 ` dpdklab
2025-11-28 20:06 ` dpdklab
2025-11-28 20:17 ` dpdklab
2025-11-28 20:18 ` dpdklab
2025-11-28 20:19 ` dpdklab [this message]
2025-11-28 20:30 ` dpdklab
2025-11-28 20:38 ` 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=692a03b9.170a0220.91139.8da9SMTPIN_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).