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| pw143630-143635 [PATCH] [11/11] crypto/cnxk: add PMD API t
Date: Thu, 05 Sep 2024 10:15:19 -0700 (PDT)	[thread overview]
Message-ID: <66d9e727.170a0220.30d05.104cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240905074631.1462357-12-ktejasree@marvell.com>

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

_Performance Testing PASS_

Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Thursday, September 05 2024 07:46:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143630-143635 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#178527

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.5%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.6%                        |
+------------+---------+----------+-------------+------------------------------+

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-05 17:15 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240905074631.1462357-12-ktejasree@marvell.com>
2024-09-05  7:21 ` |SUCCESS| pw143630-143635 [PATCH 11/11] crypto/cnxk: add PMD API to get qp stats qemudev
2024-09-05  7:25 ` qemudev
2024-09-05  7:48 ` |SUCCESS| pw143635 " checkpatch
2024-09-05  8:44 ` 0-day Robot
2024-09-05  9:28 ` |PENDING| pw143630-143635 [PATCH] [11/11] crypto/cnxk: add PMD API t dpdklab
2024-09-05  9:32 ` |SUCCESS| " dpdklab
2024-09-05  9:36 ` dpdklab
2024-09-05 10:33 ` dpdklab
2024-09-05 11:54 ` dpdklab
2024-09-05 12:13 ` dpdklab
2024-09-05 12:14 ` dpdklab
2024-09-05 12:23 ` |PENDING| " dpdklab
2024-09-05 15:14 ` |SUCCESS| " dpdklab
2024-09-05 16:23 ` dpdklab
2024-09-05 16:25 ` dpdklab
2024-09-05 16:30 ` |PENDING| " dpdklab
2024-09-05 16:33 ` |SUCCESS| " dpdklab
2024-09-05 16:51 ` dpdklab
2024-09-05 16:52 ` dpdklab
2024-09-05 16:54 ` |PENDING| " dpdklab
2024-09-05 16:54 ` |SUCCESS| " dpdklab
2024-09-05 17:01 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:09 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:11 ` dpdklab
2024-09-05 17:11 ` dpdklab
2024-09-05 17:12 ` dpdklab
2024-09-05 17:12 ` dpdklab
2024-09-05 17:13 ` dpdklab
2024-09-05 17:13 ` dpdklab
2024-09-05 17:14 ` dpdklab
2024-09-05 17:15 ` dpdklab [this message]
2024-09-05 17:15 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:17 ` dpdklab
2024-09-05 17:17 ` dpdklab
2024-09-05 17:18 ` dpdklab
2024-09-05 17:19 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:21 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 17:25 ` dpdklab
2024-09-05 17:27 ` dpdklab
2024-09-05 17:36 ` |FAILURE| " dpdklab
2024-09-05 17:37 ` dpdklab
2024-09-05 17:42 ` dpdklab
2024-09-05 17:42 ` |SUCCESS| " dpdklab
2024-09-05 17:42 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:44 ` dpdklab
2024-09-05 17:44 ` dpdklab
2024-09-05 17:45 ` dpdklab
2024-09-05 17:46 ` |FAILURE| " dpdklab
2024-09-05 17:47 ` |SUCCESS| " dpdklab
2024-09-05 17:47 ` dpdklab
2024-09-05 19:31 ` dpdklab
2024-09-05 19:32 ` dpdklab
2024-09-05 19:47 ` dpdklab
2024-09-05 22:09 ` dpdklab
2024-09-05 23:09 ` dpdklab
2024-09-06  0:25 ` dpdklab
2024-09-06 23:58 ` dpdklab
2024-09-07  0:30 ` dpdklab
2024-09-18  0:51 ` dpdklab
2024-09-18  1:09 ` dpdklab
2024-09-18  1:21 ` dpdklab
2024-09-18  1:51 ` 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=66d9e727.170a0220.30d05.104cSMTPIN_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).