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| pw152528 [PATCH] [v3] common/cnxk: fix aura offset
Date: Mon, 24 Mar 2025 02:52:34 -0700 (PDT)	[thread overview]
Message-ID: <67e12b62.020a0220.390294.38c0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250324063525.2650349-1-nkishor@marvell.com>

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

_Performance Testing PASS_

Submitter: Nawal Kishor <nkishor@marvell.com>
Date: Monday, March 24 2025 06:35:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f37ee9c859f3ce08ca4364f1d8c0e70ec33ac83

152528 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#218796

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: 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.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.8%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 2.7%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 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.3%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-03-24  9:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250324063525.2650349-1-nkishor@marvell.com>
2025-03-24  6:01 ` |SUCCESS| pw152528 [PATCH v3] " qemudev
2025-03-24  6:05 ` qemudev
2025-03-24  6:36 ` checkpatch
2025-03-24  7:23 ` 0-day Robot
2025-03-24  9:13 ` |SUCCESS| pw152528 [PATCH] [v3] " dpdklab
2025-03-24  9:30 ` dpdklab
2025-03-24  9:45 ` dpdklab
2025-03-24  9:45 ` dpdklab
2025-03-24  9:49 ` dpdklab
2025-03-24  9:52 ` dpdklab [this message]
2025-03-24  9:54 ` dpdklab
2025-03-24 10:09 ` dpdklab
2025-03-24 10:16 ` dpdklab
2025-03-24 10:19 ` |PENDING| " dpdklab
2025-03-24 10:28 ` |SUCCESS| " dpdklab
2025-03-24 10:31 ` |PENDING| " dpdklab
2025-03-24 10:33 ` dpdklab
2025-03-24 11:05 ` |SUCCESS| " dpdklab
2025-03-24 11:05 ` |PENDING| " dpdklab
2025-03-24 11:20 ` |SUCCESS| " dpdklab
2025-03-24 11:21 ` dpdklab
2025-03-24 11:45 ` dpdklab
2025-03-24 11:46 ` dpdklab
2025-03-24 11:58 ` dpdklab
2025-03-24 12:11 ` dpdklab
2025-03-24 12:30 ` 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=67e12b62.020a0220.390294.38c0SMTPIN_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).