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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125175-125176 [PATCH] [2/2] test/crypto: Add SM3/SM4 test vectors for verification in test app
Date: Thu, 16 Mar 2023 04:15:08 +0000 (UTC)	[thread overview]
Message-ID: <20230316041508.DE0416011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Performance Testing PASS_

Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Thursday, March 16 2023 03:10:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8c9bfcb1553d756eb5392a56ac7813b3865c3ec7

125175-125176 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-16  4:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  4:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-18  6:03 dpdklab
2023-03-18  5:21 dpdklab
2023-03-16  6:36 dpdklab
2023-03-16  6:31 dpdklab
2023-03-16  5:52 dpdklab
2023-03-16  5:52 dpdklab
2023-03-16  4:59 dpdklab
2023-03-16  4:49 dpdklab
2023-03-16  4:45 dpdklab
2023-03-16  4:35 dpdklab
2023-03-16  4:28 dpdklab
2023-03-16  4:27 dpdklab
2023-03-16  4:25 dpdklab
2023-03-16  4:23 dpdklab
2023-03-16  4:21 dpdklab
2023-03-16  4:18 dpdklab
2023-03-16  4:16 dpdklab
2023-03-16  4:16 dpdklab
2023-03-16  4:13 dpdklab
2023-03-16  4:12 dpdklab
2023-03-16  4:05 dpdklab
2023-03-16  4:04 dpdklab
2023-03-16  4:02 dpdklab
2023-03-16  3:56 dpdklab
2023-03-16  3:56 dpdklab
2023-03-16  3:55 dpdklab
2023-03-16  3:55 dpdklab
2023-03-16  3:51 dpdklab
2023-03-16  3:50 dpdklab
     [not found] <20230316031026.32600-2-sunyang.wu@jaguarmicro.com>
2023-03-16  2:59 ` |SUCCESS| pw125175-125176 [PATCH 2/2] " qemudev
2023-03-16  3:03 ` qemudev

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=20230316041508.DE0416011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).