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| pw154572-154571 [PATCH] [v1,3/3] net/rnp: fix TSO segmenta
Date: Wed, 18 Jun 2025 08:38:41 -0700 (PDT)	[thread overview]
Message-ID: <6852dd81.170a0220.19c11d.3e29SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250618121113.17302-4-caowenbo@mucse.com>

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

_Performance Testing PASS_

Submitter: Wenbo Cao <caowenbo@mucse.com>
Date: Wednesday, June 18 2025 12:11:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:62a35bbb247e608e235a04ff2941488bc1a78941

154572-154571 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#231674

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: 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.3%                        |
+------------+---------+----------+-------------+------------------------------+

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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.5%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

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-18 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250618121113.17302-4-caowenbo@mucse.com>
2025-06-18 11:37 ` |SUCCESS| pw154572-154571 [PATCH v1 3/3] net/rnp: fix TSO segmentation for packets of 64KB qemudev
2025-06-18 11:41 ` qemudev
2025-06-18 12:12 ` |SUCCESS| pw154571 " checkpatch
2025-06-18 13:27 ` 0-day Robot
2025-06-18 15:06 ` |SUCCESS| pw154572-154571 [PATCH] [v1,3/3] net/rnp: fix TSO segmenta dpdklab
2025-06-18 15:20 ` dpdklab
2025-06-18 15:25 ` dpdklab
2025-06-18 15:26 ` dpdklab
2025-06-18 15:38 ` dpdklab [this message]
2025-06-18 15:58 ` |PENDING| " dpdklab
2025-06-18 16:09 ` |SUCCESS| " dpdklab
2025-06-18 16:12 ` |PENDING| " dpdklab
2025-06-18 16:13 ` |SUCCESS| " dpdklab
2025-06-18 16:36 ` dpdklab
2025-06-18 17:17 ` dpdklab
2025-06-18 17:27 ` |PENDING| " dpdklab
2025-06-18 18:32 ` |FAILURE| " 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=6852dd81.170a0220.19c11d.3e29SMTPIN_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).