From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126835 [PATCH] test/crypto: fix IPsec AES CCM test vector
Date: Fri, 12 May 2023 06:40:10 -0700 (PDT) [thread overview]
Message-ID: <645e41ba.630a0220.93fe.3625SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/126835
_Performance Testing PASS_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Friday, May 12 2023 12:59:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61
126835 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26217/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-12 13:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-12 23:00 dpdklab
2023-05-12 22:51 dpdklab
2023-05-12 22:46 dpdklab
2023-05-12 22:42 dpdklab
2023-05-12 22:26 dpdklab
2023-05-12 14:54 dpdklab
2023-05-12 14:50 dpdklab
2023-05-12 14:42 dpdklab
2023-05-12 14:41 dpdklab
2023-05-12 14:30 dpdklab
2023-05-12 14:17 dpdklab
2023-05-12 14:14 dpdklab
2023-05-12 14:14 dpdklab
2023-05-12 14:14 dpdklab
2023-05-12 14:14 dpdklab
2023-05-12 14:09 dpdklab
2023-05-12 14:09 dpdklab
2023-05-12 14:09 dpdklab
2023-05-12 14:05 dpdklab
2023-05-12 14:02 dpdklab
2023-05-12 13:59 dpdklab
2023-05-12 13:49 dpdklab
2023-05-12 13:46 dpdklab
2023-05-12 13:46 dpdklab
2023-05-12 13:39 dpdklab
2023-05-12 13:38 dpdklab
2023-05-12 13:34 dpdklab
2023-05-12 13:32 dpdklab
[not found] <20230512125933.1131522-1-ktejasree@marvell.com>
2023-05-12 12:59 ` qemudev
2023-05-12 13:00 ` checkpatch
2023-05-12 13:05 ` qemudev
2023-05-12 14:00 ` 0-day Robot
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=645e41ba.630a0220.93fe.3625SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.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).