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: [dpdk-test-report] |SUCCESS| pw96897-96906 [PATCH] [v3, 10/10] ipsec: add ol_flags support
Date: Fri, 13 Aug 2021 09:26:30 -0400 (EDT) [thread overview]
Message-ID: <20210813132630.D92C2446@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/96906
_Performance Testing PASS_
Submitter: Nicolau, Radu <radu.nicolau@intel.com>
Date: Friday, August 13 2021 09:30:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ac3f3d76e9507a93bcf48d165ffd3a1faba08bb
96897-96906 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.7% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18200/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-13 13:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 13:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-17 0:28 dpdklab
2021-08-16 23:54 dpdklab
2021-08-16 23:42 dpdklab
2021-08-16 23:29 dpdklab
2021-08-16 23:16 dpdklab
2021-08-16 23:04 dpdklab
2021-08-16 22:51 dpdklab
2021-08-16 20:07 dpdklab
2021-08-16 19:55 dpdklab
2021-08-16 19:50 dpdklab
2021-08-16 19:49 dpdklab
2021-08-16 19:36 dpdklab
2021-08-16 19:34 dpdklab
2021-08-16 19:33 dpdklab
2021-08-16 19:27 dpdklab
2021-08-16 19:27 dpdklab
2021-08-16 19:16 dpdklab
2021-08-16 19:07 dpdklab
2021-08-16 18:00 dpdklab
2021-08-16 17:45 dpdklab
2021-08-13 16:11 dpdklab
2021-08-13 15:45 dpdklab
2021-08-13 15:29 dpdklab
2021-08-13 14:59 dpdklab
2021-08-13 14:36 dpdklab
2021-08-13 13:56 dpdklab
2021-08-13 13:41 dpdklab
2021-08-13 13:25 dpdklab
2021-08-13 13:10 dpdklab
2021-08-13 13:06 dpdklab
2021-08-13 13:03 dpdklab
2021-08-13 12:59 dpdklab
2021-08-13 12:55 dpdklab
2021-08-13 12:55 dpdklab
2021-08-13 12:54 dpdklab
2021-08-13 12:48 dpdklab
2021-08-13 12:47 dpdklab
2021-08-13 12:47 dpdklab
2021-08-13 12:39 dpdklab
2021-08-13 12:38 dpdklab
2021-08-13 12:36 dpdklab
2021-08-13 12:36 dpdklab
2021-08-13 12:26 dpdklab
2021-08-13 12:25 dpdklab
2021-08-13 12:22 dpdklab
2021-08-13 12:16 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=20210813132630.D92C2446@noxus.dpdklab.iol.unh.edu \
--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).