From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130039-130040 [PATCH] [2/2] test/crypto: add security te
Date: Thu, 10 Aug 2023 09:08:49 -0700 (PDT) [thread overview]
Message-ID: <64d50b91.c80a0220.d8087.4619SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/130040
_Performance Testing PASS_
Submitter: David Coyle <david.coyle@intel.com>
Date: Wednesday, August 09 2023 10:14:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130039-130040 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27262/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 16:08 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 16:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 2:24 dpdklab
2023-08-14 2:17 dpdklab
2023-08-14 2:14 dpdklab
2023-08-14 2:13 dpdklab
2023-08-14 2:13 dpdklab
2023-08-14 2:12 dpdklab
2023-08-14 2:10 dpdklab
2023-08-14 2:10 dpdklab
2023-08-14 2:08 dpdklab
2023-08-14 2:08 dpdklab
2023-08-14 2:07 dpdklab
2023-08-13 22:28 dpdklab
2023-08-13 19:19 dpdklab
2023-08-11 22:31 dpdklab
2023-08-11 22:29 dpdklab
2023-08-11 21:19 dpdklab
2023-08-11 21:13 dpdklab
2023-08-11 21:11 dpdklab
2023-08-11 21:09 dpdklab
2023-08-11 20:47 dpdklab
2023-08-11 20:42 dpdklab
2023-08-11 20:35 dpdklab
2023-08-11 20:28 dpdklab
2023-08-11 20:14 dpdklab
2023-08-11 9:01 dpdklab
2023-08-11 6:51 dpdklab
2023-08-11 6:33 dpdklab
2023-08-11 6:02 dpdklab
2023-08-11 6:01 dpdklab
2023-08-11 6:00 dpdklab
2023-08-11 5:54 dpdklab
2023-08-11 5:52 dpdklab
2023-08-11 5:52 dpdklab
2023-08-11 5:50 dpdklab
2023-08-11 5:50 dpdklab
2023-08-11 5:49 dpdklab
2023-08-11 5:48 dpdklab
2023-08-11 5:28 dpdklab
2023-08-11 5:26 dpdklab
2023-08-11 5:13 dpdklab
2023-08-11 5:11 dpdklab
2023-08-11 5:10 dpdklab
2023-08-11 5:05 dpdklab
2023-08-11 5:04 dpdklab
2023-08-11 5:00 dpdklab
2023-08-11 4:59 dpdklab
2023-08-11 4:38 dpdklab
2023-08-11 4:38 dpdklab
2023-08-11 4:38 dpdklab
2023-08-11 4:34 dpdklab
2023-08-11 4:28 dpdklab
2023-08-11 4:24 dpdklab
2023-08-11 4:24 dpdklab
2023-08-11 4:24 dpdklab
2023-08-11 4:24 dpdklab
2023-08-11 4:23 dpdklab
2023-08-11 4:23 dpdklab
2023-08-11 4:21 dpdklab
2023-08-11 4:21 dpdklab
2023-08-11 4:20 dpdklab
2023-08-11 4:18 dpdklab
2023-08-11 4:18 dpdklab
2023-08-11 4:18 dpdklab
2023-08-11 4:13 dpdklab
2023-08-11 4:13 dpdklab
2023-08-11 2:54 dpdklab
2023-08-10 22:26 dpdklab
2023-08-10 21:41 dpdklab
2023-08-10 21:38 dpdklab
2023-08-10 21:21 dpdklab
2023-08-10 20:43 dpdklab
2023-08-10 20:42 dpdklab
2023-08-10 20:02 dpdklab
2023-08-10 20:01 dpdklab
2023-08-10 19:19 dpdklab
2023-08-10 19:14 dpdklab
2023-08-10 19:11 dpdklab
2023-08-10 19:04 dpdklab
2023-08-10 18:44 dpdklab
2023-08-10 18:44 dpdklab
2023-08-10 18:44 dpdklab
2023-08-10 18:43 dpdklab
2023-08-10 18:39 dpdklab
2023-08-10 18:34 dpdklab
2023-08-10 18:32 dpdklab
2023-08-10 18:21 dpdklab
2023-08-10 18:12 dpdklab
2023-08-10 18:09 dpdklab
2023-08-10 18:07 dpdklab
2023-08-10 18:05 dpdklab
2023-08-10 17:59 dpdklab
2023-08-10 17:49 dpdklab
2023-08-10 17:36 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:20 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:10 dpdklab
2023-08-10 17:09 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:58 dpdklab
2023-08-10 16:57 dpdklab
2023-08-10 16:57 dpdklab
2023-08-10 16:57 dpdklab
2023-08-10 16:56 dpdklab
2023-08-10 16:51 dpdklab
2023-08-10 16:19 dpdklab
2023-08-10 16:10 dpdklab
2023-08-10 16:02 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=64d50b91.c80a0220.d8087.4619SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).