From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135694 [PATCH] app/test-crypto-perf: fix invalid mbuf ne
Date: Wed, 03 Jan 2024 10:06:21 -0800 (PST) [thread overview]
Message-ID: <6595a21d.170a0220.a70dd.2da7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135694
_Performance Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Wednesday, January 03 2024 03:53:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135694 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28774/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-03 18:06 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 18:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 7:32 dpdklab
2024-01-04 20:34 dpdklab
2024-01-04 4:26 dpdklab
2024-01-03 21:47 dpdklab
2024-01-03 21:45 dpdklab
2024-01-03 21:38 dpdklab
2024-01-03 19:31 dpdklab
2024-01-03 19:07 dpdklab
2024-01-03 18:55 dpdklab
2024-01-03 18:50 dpdklab
2024-01-03 18:47 dpdklab
2024-01-03 18:45 dpdklab
2024-01-03 18:44 dpdklab
2024-01-03 18:44 dpdklab
2024-01-03 18:42 dpdklab
2024-01-03 18:42 dpdklab
2024-01-03 18:41 dpdklab
2024-01-03 18:39 dpdklab
2024-01-03 18:38 dpdklab
2024-01-03 18:38 dpdklab
2024-01-03 18:37 dpdklab
2024-01-03 18:33 dpdklab
2024-01-03 18:32 dpdklab
2024-01-03 18:32 dpdklab
2024-01-03 18:30 dpdklab
2024-01-03 18:30 dpdklab
2024-01-03 18:28 dpdklab
2024-01-03 18:26 dpdklab
2024-01-03 18:26 dpdklab
2024-01-03 18:26 dpdklab
2024-01-03 18:25 dpdklab
2024-01-03 18:25 dpdklab
2024-01-03 18:23 dpdklab
2024-01-03 18:22 dpdklab
2024-01-03 18:21 dpdklab
2024-01-03 18:21 dpdklab
2024-01-03 18:18 dpdklab
2024-01-03 18:17 dpdklab
2024-01-03 18:17 dpdklab
2024-01-03 18:16 dpdklab
2024-01-03 18:16 dpdklab
2024-01-03 18:16 dpdklab
2024-01-03 18:15 dpdklab
2024-01-03 18:15 dpdklab
2024-01-03 18:15 dpdklab
2024-01-03 18:15 dpdklab
2024-01-03 18:14 dpdklab
2024-01-03 18:14 dpdklab
2024-01-03 18:13 dpdklab
2024-01-03 18:12 dpdklab
2024-01-03 18:12 dpdklab
2024-01-03 18:12 dpdklab
2024-01-03 18:12 dpdklab
2024-01-03 18:10 dpdklab
2024-01-03 18:10 dpdklab
2024-01-03 18:09 dpdklab
2024-01-03 18:08 dpdklab
2024-01-03 18:07 dpdklab
2024-01-03 17:58 dpdklab
2024-01-03 17:56 dpdklab
2024-01-03 17:52 dpdklab
2024-01-03 17:51 dpdklab
2024-01-03 17:51 dpdklab
2024-01-03 17:50 dpdklab
2024-01-03 17:50 dpdklab
2024-01-03 17:41 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=6595a21d.170a0220.a70dd.2da7SMTPIN_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).