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| pw137426 [PATCH] [v4] crypto/ipsec_mb: unified IPsec MB in
Date: Wed, 28 Feb 2024 05:42:17 -0800 (PST) [thread overview]
Message-ID: <65df3839.050a0220.e0b80.35a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228113301.934291-1-brian.dooley@intel.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137426
_Performance Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Wednesday, February 28 2024 11:33:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137426 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29315/
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-02-28 13:42 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228113301.934291-1-brian.dooley@intel.com>
2024-02-28 11:10 ` |SUCCESS| pw137426 [PATCH v4] crypto/ipsec_mb: unified IPsec MB interface qemudev
2024-02-28 11:14 ` qemudev
2024-02-28 11:33 ` checkpatch
2024-02-28 12:25 ` 0-day Robot
2024-02-28 13:12 ` |SUCCESS| pw137426 [PATCH] [v4] crypto/ipsec_mb: unified IPsec MB in dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:26 ` dpdklab
2024-02-28 13:42 ` dpdklab [this message]
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 14:08 ` dpdklab
2024-02-28 14:23 ` dpdklab
2024-02-28 14:28 ` dpdklab
2024-02-28 14:28 ` dpdklab
2024-02-28 14:30 ` |WARNING| " dpdklab
2024-02-28 14:31 ` |SUCCESS| " dpdklab
2024-02-28 14:31 ` |WARNING| " dpdklab
2024-02-28 14:32 ` |SUCCESS| " dpdklab
2024-02-28 14:32 ` dpdklab
2024-02-28 14:32 ` dpdklab
2024-02-28 14:33 ` |WARNING| " dpdklab
2024-02-28 14:33 ` |SUCCESS| " dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:34 ` |WARNING| " dpdklab
2024-02-28 14:34 ` |SUCCESS| " dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:36 ` |WARNING| " dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:37 ` |SUCCESS| " dpdklab
2024-02-28 14:37 ` |WARNING| " dpdklab
2024-02-28 14:37 ` |SUCCESS| " dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:42 ` |WARNING| " dpdklab
2024-02-28 14:42 ` |SUCCESS| " dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:51 ` |WARNING| " dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 15:56 ` |SUCCESS| " dpdklab
2024-02-28 18:03 ` dpdklab
2024-02-28 19:52 ` dpdklab
2024-02-28 20:34 ` dpdklab
2024-02-29 11:01 ` dpdklab
2024-02-29 22:36 ` |FAILURE| " dpdklab
2024-02-29 22:40 ` |SUCCESS| " dpdklab
2024-02-29 22:50 ` dpdklab
2024-02-29 22:53 ` dpdklab
2024-03-01 17:37 ` dpdklab
2024-03-01 18:05 ` |FAILURE| " dpdklab
2024-03-01 18:39 ` |SUCCESS| " dpdklab
2024-03-05 20:07 ` dpdklab
2024-03-06 4:05 ` |FAILURE| " 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=65df3839.050a0220.e0b80.35a5SMTPIN_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).