From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136852 [PATCH] [v2] cryptodev: speed up ops pool create
Date: Fri, 16 Feb 2024 10:10:07 -0800 (PST) [thread overview]
Message-ID: <65cfa4ff.9d0a0220.bd123.1408SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136852
_Performance Testing PASS_
Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Friday, February 16 2024 17:03:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c
136852 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29173/
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-16 18:10 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 18:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 4:19 dpdklab
2024-02-17 4:12 dpdklab
2024-02-16 20:06 dpdklab
2024-02-16 20:01 dpdklab
2024-02-16 19:54 dpdklab
2024-02-16 19:48 dpdklab
2024-02-16 19:47 dpdklab
2024-02-16 19:45 dpdklab
2024-02-16 19:34 dpdklab
2024-02-16 19:31 dpdklab
2024-02-16 19:28 dpdklab
2024-02-16 19:26 dpdklab
2024-02-16 19:24 dpdklab
2024-02-16 19:21 dpdklab
2024-02-16 19:17 dpdklab
2024-02-16 19:16 dpdklab
2024-02-16 19:12 dpdklab
2024-02-16 19:12 dpdklab
2024-02-16 19:11 dpdklab
2024-02-16 19:10 dpdklab
2024-02-16 19:06 dpdklab
2024-02-16 19:06 dpdklab
2024-02-16 19:05 dpdklab
2024-02-16 19:04 dpdklab
2024-02-16 19:04 dpdklab
2024-02-16 19:03 dpdklab
2024-02-16 19:01 dpdklab
2024-02-16 19:00 dpdklab
2024-02-16 19:00 dpdklab
2024-02-16 18:58 dpdklab
2024-02-16 18:55 dpdklab
2024-02-16 18:53 dpdklab
2024-02-16 18:53 dpdklab
2024-02-16 18:52 dpdklab
2024-02-16 18:51 dpdklab
2024-02-16 18:49 dpdklab
2024-02-16 18:49 dpdklab
2024-02-16 18:48 dpdklab
2024-02-16 18:46 dpdklab
2024-02-16 18:45 dpdklab
2024-02-16 18:44 dpdklab
2024-02-16 18:44 dpdklab
2024-02-16 18:40 dpdklab
2024-02-16 18:38 dpdklab
2024-02-16 18:37 dpdklab
2024-02-16 18:36 dpdklab
2024-02-16 18:36 dpdklab
2024-02-16 18:35 dpdklab
2024-02-16 18:35 dpdklab
2024-02-16 18:34 dpdklab
2024-02-16 18:32 dpdklab
2024-02-16 18:32 dpdklab
2024-02-16 18:32 dpdklab
2024-02-16 18:31 dpdklab
2024-02-16 18:31 dpdklab
2024-02-16 18:31 dpdklab
2024-02-16 18:30 dpdklab
2024-02-16 18:30 dpdklab
2024-02-16 18:28 dpdklab
2024-02-16 18:28 dpdklab
2024-02-16 18:28 dpdklab
2024-02-16 18:28 dpdklab
2024-02-16 18:27 dpdklab
2024-02-16 18:26 dpdklab
2024-02-16 18:26 dpdklab
2024-02-16 18:24 dpdklab
2024-02-16 18:23 dpdklab
2024-02-16 18:15 dpdklab
[not found] <20240216170334.55210-1-andrew.boyer@amd.com>
2024-02-16 16:41 ` |SUCCESS| pw136852 [PATCH v2] " qemudev
2024-02-16 16:45 ` qemudev
2024-02-16 17:05 ` checkpatch
2024-02-16 18:05 ` 0-day Robot
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=65cfa4ff.9d0a0220.bd123.1408SMTPIN_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).