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| pw153476-153480 [PATCH] [v4,9/9] app/test: add zsda crypto
Date: Fri, 16 May 2025 04:21:43 -0700 (PDT)	[thread overview]
Message-ID: <68271fc7.050a0220.9652f.27bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250516072752.1971299-10-li.hanxiao@zte.com.cn>

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

_Performance Testing PASS_

Submitter: Hanxiao Li <li.hanxiao@zte.com.cn>
Date: Friday, May 16 2025 07:27:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:dcf9f9363aa9b4163d241caf8b26a84ca0c0006b

153476-153480 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#226200

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           | 166.7%                       |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 167.4%                       |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 168.4%                       |
+------------+---------+----------+-------------+------------------------------+

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.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-16 11:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250516072752.1971299-10-li.hanxiao@zte.com.cn>
2025-05-16  6:59 ` |SUCCESS| pw153476-153480 [PATCH v4 9/9] app/test: add zsda cryptodev test qemudev
2025-05-16  7:03 ` qemudev
2025-05-16  7:33 ` |SUCCESS| pw153480 " checkpatch
2025-05-16  8:43 ` 0-day Robot
2025-05-16 11:06 ` |SUCCESS| pw153476-153480 [PATCH] [v4,9/9] app/test: add zsda crypto dpdklab
2025-05-16 11:18 ` dpdklab
2025-05-16 11:18 ` dpdklab
2025-05-16 11:21 ` dpdklab [this message]
2025-05-16 11:29 ` dpdklab
2025-05-16 11:34 ` dpdklab
2025-05-16 11:45 ` dpdklab
2025-05-16 11:56 ` dpdklab
2025-05-16 12:01 ` dpdklab
2025-05-16 12:25 ` |PENDING| " dpdklab
2025-05-16 12:56 ` dpdklab
2025-05-16 13:34 ` dpdklab
2025-05-16 13:37 ` |SUCCESS| " dpdklab
2025-05-16 14:03 ` dpdklab
2025-05-16 14:25 ` dpdklab
2025-05-16 14:59 ` dpdklab
2025-05-16 15:00 ` dpdklab
2025-05-16 15:00 ` dpdklab
2025-05-16 15:01 ` dpdklab
2025-05-16 16:23 ` dpdklab
2025-05-16 21:58 ` 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=68271fc7.050a0220.9652f.27bbSMTPIN_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).