automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw102573 [PATCH] crypto/qat: fix not set status in RSA decryption
Date: Thu, 21 Oct 2021 19:56:55 +0000 (UTC)	[thread overview]
Message-ID: <20211021195655.EC9366045A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

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

_Performance Testing PASS_

Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thursday, October 21 2021 10:05:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3ac2dffae88e8eb5c374b1fdd40d605014526510

102573 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 0.2%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-21 19:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 19:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-22  4:27 dpdklab
2021-10-22  4:14 dpdklab
2021-10-22  4:01 dpdklab
2021-10-22  3:46 dpdklab
2021-10-22  3:32 dpdklab
2021-10-22  3:19 dpdklab
2021-10-21 22:05 dpdklab
2021-10-21 21:54 dpdklab
2021-10-21 21:31 dpdklab
2021-10-21 21:20 dpdklab
2021-10-21 21:19 dpdklab
2021-10-21 20:57 dpdklab
2021-10-21 20:36 dpdklab
2021-10-21 20:23 dpdklab
2021-10-21 20:18 dpdklab
2021-10-21 20:18 dpdklab
2021-10-21 20:18 dpdklab
2021-10-21 20:12 dpdklab
2021-10-21 20:06 dpdklab
2021-10-21 20:05 dpdklab
2021-10-21 20:00 dpdklab
2021-10-21 19:55 dpdklab
2021-10-21 19:54 dpdklab
2021-10-21 19:44 dpdklab
     [not found] <20211021100543.16146-1-arkadiuszx.kusztal@intel.com>
2021-10-21 10:06 ` checkpatch

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=20211021195655.EC9366045A@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --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).