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| pw138284-138304 [PATCH] [v4,21/21] test/security: add out
Date: Tue, 12 Mar 2024 23:51:25 -0700 (PDT) [thread overview]
Message-ID: <65f14ced.c80a0220.69d1a.e631SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240313055030.1685039-22-asasidharan@marvell.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138304
_Performance Testing PASS_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Wednesday, March 13 2024 05:50:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138284-138304 --> 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-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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29529/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-13 6:51 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313055030.1685039-22-asasidharan@marvell.com>
2024-03-13 5:30 ` |SUCCESS| pw138284-138304 [PATCH v4 21/21] test/security: add out of place sgl test case for TLS 1.2 qemudev
2024-03-13 5:35 ` qemudev
2024-03-13 5:55 ` |SUCCESS| pw138304 " checkpatch
2024-03-13 6:42 ` |SUCCESS| pw138284-138304 [PATCH] [v4,21/21] test/security: add out dpdklab
2024-03-13 6:42 ` dpdklab
2024-03-13 6:43 ` dpdklab
2024-03-13 6:43 ` dpdklab
2024-03-13 6:43 ` |SUCCESS| pw138304 [PATCH v4 21/21] test/security: add out of place sgl test case for TLS 1.2 0-day Robot
2024-03-13 6:50 ` |SUCCESS| pw138284-138304 [PATCH] [v4,21/21] test/security: add out dpdklab
2024-03-13 6:50 ` dpdklab
2024-03-13 6:50 ` dpdklab
2024-03-13 6:50 ` dpdklab
2024-03-13 6:50 ` dpdklab
2024-03-13 6:51 ` dpdklab
2024-03-13 6:51 ` dpdklab
2024-03-13 6:51 ` dpdklab [this message]
2024-03-13 6:51 ` dpdklab
2024-03-13 6:52 ` dpdklab
2024-03-13 6:52 ` dpdklab
2024-03-13 6:53 ` dpdklab
2024-03-13 6:53 ` dpdklab
2024-03-13 6:53 ` dpdklab
2024-03-13 6:53 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:54 ` dpdklab
2024-03-13 6:55 ` dpdklab
2024-03-13 6:55 ` dpdklab
2024-03-13 6:55 ` dpdklab
2024-03-13 6:55 ` dpdklab
2024-03-13 6:56 ` dpdklab
2024-03-13 6:56 ` dpdklab
2024-03-13 6:56 ` dpdklab
2024-03-13 6:56 ` dpdklab
2024-03-13 6:56 ` dpdklab
2024-03-13 6:57 ` dpdklab
2024-03-13 6:57 ` dpdklab
2024-03-13 6:57 ` dpdklab
2024-03-13 6:57 ` dpdklab
2024-03-13 6:57 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:58 ` dpdklab
2024-03-13 6:59 ` dpdklab
2024-03-13 6:59 ` dpdklab
2024-03-13 6:59 ` dpdklab
2024-03-13 6:59 ` dpdklab
2024-03-13 6:59 ` dpdklab
2024-03-13 7:00 ` dpdklab
2024-03-13 7:00 ` dpdklab
2024-03-13 7:00 ` dpdklab
2024-03-13 7:00 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:01 ` dpdklab
2024-03-13 7:02 ` dpdklab
2024-03-13 7:02 ` dpdklab
2024-03-13 7:03 ` dpdklab
2024-03-13 7:03 ` dpdklab
2024-03-13 7:03 ` dpdklab
2024-03-13 7:03 ` dpdklab
2024-03-13 7:16 ` dpdklab
2024-03-13 7:17 ` dpdklab
2024-03-13 7:19 ` dpdklab
2024-03-13 7:21 ` dpdklab
2024-03-13 7:26 ` dpdklab
2024-03-13 8:03 ` dpdklab
2024-03-16 20:25 ` dpdklab
2024-03-16 21:01 ` 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=65f14ced.c80a0220.69d1a.e631SMTPIN_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).