From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137093 [PATCH] [v2] examples/ipsec-secgw: fix cryptodev
Date: Fri, 23 Feb 2024 16:49:06 -0800 (PST) [thread overview]
Message-ID: <65d93d02.050a0220.8dd66.03bcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137093
_Performance Testing PASS_
Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Friday, February 23 2024 11:01:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137093 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.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.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29240/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-24 0:49 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 0:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 12:13 dpdklab
2024-02-24 11:45 dpdklab
2024-02-24 11:26 dpdklab
2024-02-24 7:49 dpdklab
2024-02-24 4:16 dpdklab
2024-02-24 3:37 dpdklab
2024-02-24 3:36 dpdklab
2024-02-24 3:21 dpdklab
2024-02-24 3:00 dpdklab
2024-02-24 2:59 dpdklab
2024-02-24 2:57 dpdklab
2024-02-24 2:54 dpdklab
2024-02-24 2:53 dpdklab
2024-02-24 2:52 dpdklab
2024-02-24 2:52 dpdklab
2024-02-24 2:48 dpdklab
2024-02-24 2:48 dpdklab
2024-02-24 2:48 dpdklab
2024-02-24 2:48 dpdklab
2024-02-24 2:47 dpdklab
2024-02-24 2:47 dpdklab
2024-02-24 2:47 dpdklab
2024-02-24 2:47 dpdklab
2024-02-24 2:46 dpdklab
2024-02-24 2:45 dpdklab
2024-02-24 2:45 dpdklab
2024-02-24 2:39 dpdklab
2024-02-24 2:39 dpdklab
2024-02-24 2:39 dpdklab
2024-02-24 2:37 dpdklab
2024-02-24 2:35 dpdklab
2024-02-24 2:33 dpdklab
2024-02-24 2:25 dpdklab
2024-02-24 2:25 dpdklab
2024-02-24 2:25 dpdklab
2024-02-24 2:24 dpdklab
2024-02-24 2:23 dpdklab
2024-02-24 2:23 dpdklab
2024-02-24 2:22 dpdklab
2024-02-24 2:20 dpdklab
2024-02-24 2:20 dpdklab
2024-02-24 2:19 dpdklab
2024-02-24 2:13 dpdklab
2024-02-24 2:13 dpdklab
2024-02-24 2:06 dpdklab
2024-02-24 1:53 dpdklab
2024-02-24 1:51 dpdklab
2024-02-24 1:16 dpdklab
2024-02-24 1:12 dpdklab
2024-02-24 1:03 dpdklab
2024-02-24 1:03 dpdklab
2024-02-24 1:02 dpdklab
2024-02-24 1:02 dpdklab
2024-02-24 1:02 dpdklab
2024-02-24 1:02 dpdklab
2024-02-24 0:55 dpdklab
2024-02-24 0:49 dpdklab
2024-02-24 0:39 dpdklab
2024-02-24 0:35 dpdklab
2024-02-24 0:35 dpdklab
2024-02-24 0:34 dpdklab
2024-02-24 0:34 dpdklab
2024-02-24 0:33 dpdklab
2024-02-24 0:30 dpdklab
2024-02-24 0:30 dpdklab
2024-02-24 0:29 dpdklab
2024-02-24 0:28 dpdklab
2024-02-24 0:21 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=65d93d02.050a0220.8dd66.03bcSMTPIN_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).