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| pw141161-141166 [PATCH] [v1,6/6] app/crypto-perf: support
Date: Sat, 15 Jun 2024 10:35:32 -0700 (PDT)	[thread overview]
Message-ID: <666dd0e4.050a0220.4ec8c.2241SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240615115309.2678-7-gmuthukrishn@marvell.com>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141166

_Performance Testing PASS_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Saturday, June 15 2024 11:53:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6909b48776badc05542a410ebd34bcfec4c248bf

141161-141166 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: Unknown
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-15 17:35 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240615115309.2678-7-gmuthukrishn@marvell.com>
2024-06-15 11:31 ` |SUCCESS| pw141161-141166 [PATCH v1 6/6] app/crypto-perf: support ECDSA qemudev
2024-06-15 11:35 ` qemudev
2024-06-15 11:56 ` |SUCCESS| pw141166 " checkpatch
2024-06-15 17:33 ` |SUCCESS| pw141161-141166 [PATCH] [v1,6/6] app/crypto-perf: support dpdklab
2024-06-15 17:35 ` dpdklab [this message]
2024-06-15 17:36 ` dpdklab
2024-06-15 17:37 ` dpdklab
2024-06-15 17:40 ` dpdklab
2024-06-15 17:41 ` dpdklab
2024-06-15 17:42 ` dpdklab
2024-06-15 18:02 ` dpdklab
2024-06-15 18:07 ` dpdklab
2024-06-15 18:07 ` dpdklab
2024-06-15 18:07 ` dpdklab
2024-06-15 18:08 ` dpdklab
2024-06-15 18:08 ` dpdklab
2024-06-15 18:08 ` dpdklab
2024-06-15 18:09 ` dpdklab
2024-06-15 18:10 ` dpdklab
2024-06-15 18:11 ` dpdklab
2024-06-15 18:21 ` dpdklab
2024-06-15 18:24 ` dpdklab
2024-06-15 18:24 ` dpdklab
2024-06-15 18:26 ` dpdklab
2024-06-15 18:27 ` dpdklab
2024-06-15 18:28 ` dpdklab
2024-06-15 18:29 ` dpdklab
2024-06-15 18:30 ` dpdklab
2024-06-15 18:32 ` dpdklab
2024-06-15 18:32 ` dpdklab
2024-06-15 18:34 ` dpdklab
2024-06-15 18:36 ` dpdklab
2024-06-15 18:36 ` dpdklab
2024-06-15 18:36 ` dpdklab
2024-06-15 18:37 ` dpdklab
2024-06-15 18:37 ` dpdklab
2024-06-15 18:38 ` dpdklab
2024-06-15 18:38 ` dpdklab
2024-06-15 18:40 ` dpdklab
2024-06-15 18:40 ` dpdklab
2024-06-15 18:40 ` dpdklab
2024-06-15 18:41 ` dpdklab
2024-06-15 18:42 ` dpdklab
2024-06-15 18:42 ` dpdklab
2024-06-15 18:43 ` dpdklab
2024-06-15 18:44 ` dpdklab
2024-06-15 18:45 ` dpdklab
2024-06-15 18:45 ` dpdklab
2024-06-15 18:45 ` dpdklab
2024-06-15 18:46 ` dpdklab
2024-06-15 18:46 ` dpdklab
2024-06-15 18:47 ` dpdklab
2024-06-15 18:48 ` dpdklab
2024-06-15 18:48 ` dpdklab
2024-06-15 18:48 ` dpdklab
2024-06-15 18:50 ` dpdklab
2024-06-15 18:51 ` dpdklab
2024-06-15 18:52 ` dpdklab
2024-06-15 18:52 ` dpdklab
2024-06-15 18:53 ` dpdklab
2024-06-15 18:53 ` dpdklab
2024-06-15 18:53 ` dpdklab
2024-06-15 18:53 ` dpdklab
2024-06-15 18:54 ` dpdklab
2024-06-15 18:55 ` dpdklab
2024-06-15 18:57 ` dpdklab
2024-06-15 18:57 ` dpdklab
2024-06-15 18:58 ` dpdklab
2024-06-15 19:01 ` dpdklab
2024-06-15 19:02 ` dpdklab
2024-06-15 19:03 ` dpdklab
2024-06-15 19:05 ` dpdklab
2024-06-15 19:06 ` dpdklab
2024-06-15 19:07 ` dpdklab
2024-06-15 19:08 ` dpdklab
2024-06-15 19:08 ` dpdklab
2024-06-15 19:09 ` dpdklab
2024-06-15 19:10 ` dpdklab
2024-06-15 19:10 ` dpdklab
2024-06-15 19:12 ` dpdklab
2024-06-15 19:14 ` dpdklab
2024-06-15 19:16 ` dpdklab
2024-06-15 19:17 ` dpdklab
2024-06-15 19:17 ` dpdklab
2024-06-15 19:18 ` dpdklab
2024-06-15 19:18 ` dpdklab
2024-06-15 19:19 ` dpdklab
2024-06-15 19:20 ` dpdklab
2024-06-15 19:21 ` dpdklab
2024-06-15 19:22 ` dpdklab
2024-06-15 19:22 ` dpdklab
2024-06-15 19:23 ` dpdklab
2024-06-15 19:24 ` dpdklab
2024-06-15 19:24 ` dpdklab
2024-06-15 19:24 ` dpdklab
2024-06-15 19:25 ` dpdklab
2024-06-15 19:26 ` dpdklab
2024-06-15 19:26 ` dpdklab
2024-06-15 19:29 ` dpdklab
2024-06-15 19:32 ` dpdklab
2024-06-15 19:33 ` dpdklab
2024-06-15 19:34 ` dpdklab
2024-06-15 19:35 ` dpdklab
2024-06-15 19:38 ` dpdklab
2024-06-15 19:40 ` dpdklab
2024-06-15 19:41 ` dpdklab
2024-06-15 19:48 ` dpdklab
2024-06-15 19:52 ` dpdklab
2024-06-15 19:52 ` dpdklab
2024-06-15 20:12 ` dpdklab
2024-06-15 20:19 ` dpdklab
2024-06-15 20:31 ` 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=666dd0e4.050a0220.4ec8c.2241SMTPIN_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).