From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135431-135454 [PATCH] [24/24] crypto/cnxk: add CPT SG mo
Date: Thu, 21 Dec 2023 07:10:53 -0800 (PST) [thread overview]
Message-ID: <6584557d.050a0220.dbcec.3a27SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135454
_Performance Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Thursday, December 21 2023 12:35:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135431-135454 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28715/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-21 15:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:10 dpdklab [this message]
2023-12-21 15:20 dpdklab
2023-12-21 15:27 dpdklab
2023-12-21 15:28 dpdklab
2023-12-21 15:31 dpdklab
2023-12-21 15:48 dpdklab
2023-12-21 15:49 dpdklab
2023-12-21 15:52 dpdklab
2023-12-21 15:52 dpdklab
2023-12-21 15:52 dpdklab
2023-12-21 15:53 dpdklab
2023-12-21 15:53 dpdklab
2023-12-21 15:57 dpdklab
2023-12-21 15:59 dpdklab
2023-12-21 16:02 dpdklab
2023-12-21 16:10 dpdklab
2023-12-21 16:10 dpdklab
2023-12-21 16:12 dpdklab
2023-12-21 16:12 dpdklab
2023-12-21 16:12 dpdklab
2023-12-21 16:13 dpdklab
2023-12-21 16:15 dpdklab
2023-12-21 16:17 dpdklab
2023-12-21 16:22 dpdklab
2023-12-21 16:24 dpdklab
2023-12-21 16:26 dpdklab
2023-12-21 16:27 dpdklab
2023-12-21 16:27 dpdklab
2023-12-21 16:28 dpdklab
2023-12-21 16:28 dpdklab
2023-12-21 16:31 dpdklab
2023-12-21 16:31 dpdklab
2023-12-21 16:31 dpdklab
2023-12-21 16:33 dpdklab
2023-12-21 16:36 dpdklab
2023-12-21 16:37 dpdklab
2023-12-21 16:38 dpdklab
2023-12-21 16:39 dpdklab
2023-12-21 16:39 dpdklab
2023-12-21 16:40 dpdklab
2023-12-21 16:41 dpdklab
2023-12-21 16:41 dpdklab
2023-12-21 16:44 dpdklab
2023-12-21 16:45 dpdklab
2023-12-21 16:46 dpdklab
2023-12-21 16:47 dpdklab
2023-12-21 16:49 dpdklab
2023-12-21 16:49 dpdklab
2023-12-21 16:50 dpdklab
2023-12-21 16:51 dpdklab
2023-12-21 16:52 dpdklab
2023-12-21 16:53 dpdklab
2023-12-21 16:54 dpdklab
2023-12-21 16:56 dpdklab
2023-12-21 16:59 dpdklab
2023-12-21 17:01 dpdklab
2023-12-21 17:04 dpdklab
2023-12-21 17:06 dpdklab
2023-12-21 17:08 dpdklab
2023-12-21 17:09 dpdklab
2023-12-21 17:09 dpdklab
2023-12-21 17:20 dpdklab
2023-12-21 17:21 dpdklab
2023-12-21 18:26 dpdklab
2023-12-21 18:36 dpdklab
2023-12-21 19:05 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=6584557d.050a0220.dbcec.3a27SMTPIN_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).