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| pw143678 [PATCH] cryptodev: add asymmetric operational cap
Date: Thu, 05 Sep 2024 23:20:20 -0700 (PDT)	[thread overview]
Message-ID: <66da9f24.170a0220.c2ce3.47abSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240905181725.2040-1-gmuthukrishn@marvell.com>

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

_Performance Testing PASS_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, September 05 2024 18:17:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

143678 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#178681

Test environment and result as below:

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

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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

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-06  6:20 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240905181725.2040-1-gmuthukrishn@marvell.com>
2024-09-05 18:07 ` |SUCCESS| pw143678 [PATCH] cryptodev: add asymmetric operational capability qemudev
2024-09-05 18:11 ` qemudev
2024-09-05 18:18 ` checkpatch
2024-09-05 19:04 ` |FAILURE| " 0-day Robot
2024-09-05 22:55 ` |SUCCESS| pw143678 [PATCH] cryptodev: add asymmetric operational cap dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:09 ` dpdklab
2024-09-05 23:10 ` dpdklab
2024-09-05 23:17 ` dpdklab
2024-09-05 23:23 ` dpdklab
2024-09-05 23:26 ` |PENDING| " dpdklab
2024-09-05 23:27 ` |SUCCESS| " dpdklab
2024-09-05 23:29 ` dpdklab
2024-09-05 23:41 ` |PENDING| " dpdklab
2024-09-05 23:42 ` |SUCCESS| " dpdklab
2024-09-05 23:48 ` dpdklab
2024-09-05 23:51 ` dpdklab
2024-09-05 23:53 ` dpdklab
2024-09-05 23:53 ` dpdklab
2024-09-05 23:53 ` |PENDING| " dpdklab
2024-09-06  0:02 ` |SUCCESS| " dpdklab
2024-09-06  0:15 ` |PENDING| " dpdklab
2024-09-06  0:18 ` dpdklab
2024-09-06  0:40 ` |SUCCESS| " dpdklab
2024-09-06  5:26 ` dpdklab
2024-09-06  5:48 ` dpdklab
2024-09-06  6:01 ` dpdklab
2024-09-06  6:02 ` dpdklab
2024-09-06  6:18 ` dpdklab
2024-09-06  6:20 ` dpdklab [this message]
2024-09-06  6:20 ` dpdklab
2024-09-06  6:27 ` dpdklab
2024-09-06  6:33 ` |FAILURE| " dpdklab
2024-09-06  6:33 ` dpdklab
2024-09-06  6:33 ` dpdklab
2024-09-06  6:33 ` dpdklab
2024-09-06  6:33 ` dpdklab
2024-09-06  6:34 ` dpdklab
2024-09-06  6:34 ` dpdklab
2024-09-06  6:34 ` dpdklab
2024-09-06  6:34 ` dpdklab
2024-09-06  6:35 ` |SUCCESS| " dpdklab
2024-09-06  6:36 ` |FAILURE| " dpdklab
2024-09-06  6:38 ` dpdklab
2024-09-06  6:38 ` dpdklab
2024-09-06  6:38 ` dpdklab
2024-09-06  6:40 ` dpdklab
2024-09-06  6:40 ` dpdklab
2024-09-06  6:42 ` dpdklab
2024-09-06  6:44 ` dpdklab
2024-09-06  6:49 ` dpdklab
2024-09-06  6:49 ` dpdklab
2024-09-06  6:50 ` dpdklab
2024-09-06  6:52 ` |SUCCESS| " dpdklab
2024-09-06  7:07 ` |FAILURE| " dpdklab
2024-09-06  7:07 ` dpdklab
2024-09-06  7:17 ` dpdklab
2024-09-06  7:19 ` dpdklab
2024-09-06  7:19 ` dpdklab
2024-09-06  7:41 ` dpdklab
2024-09-06  7:43 ` dpdklab
2024-09-06  7:44 ` dpdklab
2024-09-06  7:49 ` dpdklab
2024-09-06  7:50 ` dpdklab
2024-09-06  7:57 ` dpdklab
2024-09-06  7:59 ` dpdklab
2024-09-06  8:00 ` dpdklab
2024-09-06  8:00 ` dpdklab
2024-09-06  8:02 ` dpdklab
2024-09-06  8:02 ` dpdklab
2024-09-06  8:07 ` dpdklab
2024-09-06  8:31 ` dpdklab
2024-09-06 10:12 ` dpdklab
2024-09-06 10:57 ` dpdklab
2024-09-06 10:57 ` dpdklab
2024-09-06 10:58 ` dpdklab
2024-09-06 10:59 ` dpdklab
2024-09-06 11:00 ` dpdklab
2024-09-06 11:00 ` dpdklab
2024-09-06 11:28 ` dpdklab
2024-09-07 16:20 ` |SUCCESS| " dpdklab
2024-09-07 16:53 ` dpdklab
2024-09-17 18:42 ` dpdklab
2024-09-17 19:21 ` dpdklab
2024-09-17 19:35 ` dpdklab
2024-09-17 19:54 ` 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=66da9f24.170a0220.c2ce3.47abSMTPIN_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).