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| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting
Date: Fri, 15 Mar 2024 13:07:27 -0700 (PDT)	[thread overview]
Message-ID: <65f4aa7f.050a0220.cbce3.cd6cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312075238.3319480-4-huangdengdui@huawei.com>

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

_Performance Testing PASS_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tuesday, March 12 2024 07:52:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e3faaed01e14ffdfe8f4190030540ed874184b55

138202-138203 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
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           | 4.1%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-15 20:07 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312075238.3319480-4-huangdengdui@huawei.com>
2024-03-12  7:32 ` |SUCCESS| pw138202-138203 [PATCH 3/3] app/testpmd: support setting lanes qemudev
2024-03-12  7:36 ` |FAILURE| " qemudev
2024-03-12  7:53 ` |SUCCESS| pw138203 " checkpatch
2024-03-12  8:42 ` |FAILURE| " 0-day Robot
2024-03-12  9:50 ` |SUCCESS| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting dpdklab
2024-03-12  9:59 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:14 ` dpdklab
2024-03-12 10:21 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` |SUCCESS| " dpdklab
2024-03-12 10:23 ` |FAILURE| " dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:24 ` |SUCCESS| " dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:26 ` dpdklab
2024-03-12 10:29 ` |WARNING| " dpdklab
2024-03-12 10:30 ` |SUCCESS| " dpdklab
2024-03-12 10:31 ` |WARNING| " dpdklab
2024-03-12 10:31 ` dpdklab
2024-03-12 10:32 ` |SUCCESS| " dpdklab
2024-03-12 10:32 ` dpdklab
2024-03-12 10:33 ` dpdklab
2024-03-12 10:33 ` |WARNING| " dpdklab
2024-03-12 10:34 ` dpdklab
2024-03-12 10:34 ` |SUCCESS| " dpdklab
2024-03-12 10:34 ` |FAILURE| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:35 ` |WARNING| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:36 ` dpdklab
2024-03-12 10:36 ` |FAILURE| " dpdklab
2024-03-12 10:36 ` |WARNING| " dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:37 ` dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:41 ` |FAILURE| " dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:43 ` dpdklab
2024-03-12 10:44 ` dpdklab
2024-03-12 10:50 ` dpdklab
2024-03-12 10:53 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` |SUCCESS| " dpdklab
2024-03-12 10:59 ` |FAILURE| " dpdklab
2024-03-12 11:00 ` |SUCCESS| " dpdklab
2024-03-12 11:01 ` |FAILURE| " dpdklab
2024-03-12 11:06 ` dpdklab
2024-03-12 11:07 ` |SUCCESS| " dpdklab
2024-03-12 11:08 ` |FAILURE| " dpdklab
2024-03-12 11:08 ` |SUCCESS| " dpdklab
2024-03-12 11:09 ` |FAILURE| " dpdklab
2024-03-12 11:09 ` |SUCCESS| " dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:15 ` |FAILURE| " dpdklab
2024-03-12 11:18 ` |SUCCESS| " dpdklab
2024-03-12 12:10 ` dpdklab
2024-03-12 12:24 ` dpdklab
2024-03-12 13:11 ` dpdklab
2024-03-15 20:07 ` dpdklab [this message]
2024-03-15 20:36 ` 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=65f4aa7f.050a0220.cbce3.cd6cSMTPIN_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).