From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135217 [PATCH] [v4,7/7] dts: add scatter test suite
Date: Thu, 14 Dec 2023 17:54:45 -0800 (PST) [thread overview]
Message-ID: <657bb1e5.170a0220.45221.6becSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135217
_Performance Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thursday, December 14 2023 22:10:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135217 --> 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28639/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-15 1:54 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 1:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 12:47 dpdklab
2023-12-15 5:25 dpdklab
2023-12-15 4:13 dpdklab
2023-12-15 3:42 dpdklab
2023-12-15 3:42 dpdklab
2023-12-15 3:28 dpdklab
2023-12-15 3:23 dpdklab
2023-12-15 3:23 dpdklab
2023-12-15 3:23 dpdklab
2023-12-15 3:21 dpdklab
2023-12-15 3:20 dpdklab
2023-12-15 3:18 dpdklab
2023-12-15 3:15 dpdklab
2023-12-15 3:15 dpdklab
2023-12-15 3:13 dpdklab
2023-12-15 3:12 dpdklab
2023-12-15 3:04 dpdklab
2023-12-15 3:04 dpdklab
2023-12-15 3:04 dpdklab
2023-12-15 3:02 dpdklab
2023-12-15 3:01 dpdklab
2023-12-15 3:00 dpdklab
2023-12-15 2:59 dpdklab
2023-12-15 2:59 dpdklab
2023-12-15 2:53 dpdklab
2023-12-15 2:53 dpdklab
2023-12-15 2:52 dpdklab
2023-12-15 2:48 dpdklab
2023-12-15 2:47 dpdklab
2023-12-15 2:47 dpdklab
2023-12-15 2:47 dpdklab
2023-12-15 2:47 dpdklab
2023-12-15 2:44 dpdklab
2023-12-15 2:43 dpdklab
2023-12-15 2:43 dpdklab
2023-12-15 2:43 dpdklab
2023-12-15 2:42 dpdklab
2023-12-15 2:41 dpdklab
2023-12-15 2:40 dpdklab
2023-12-15 2:40 dpdklab
2023-12-15 2:37 dpdklab
2023-12-15 2:36 dpdklab
2023-12-15 2:33 dpdklab
2023-12-15 2:31 dpdklab
2023-12-15 2:31 dpdklab
2023-12-15 2:30 dpdklab
2023-12-15 2:30 dpdklab
2023-12-15 2:29 dpdklab
2023-12-15 2:29 dpdklab
2023-12-15 2:29 dpdklab
2023-12-15 2:28 dpdklab
2023-12-15 2:27 dpdklab
2023-12-15 2:27 dpdklab
2023-12-15 2:26 dpdklab
2023-12-15 2:25 dpdklab
2023-12-15 2:25 dpdklab
2023-12-15 2:20 dpdklab
2023-12-15 2:20 dpdklab
2023-12-15 2:20 dpdklab
2023-12-15 2:19 dpdklab
2023-12-15 2:11 dpdklab
2023-12-15 2:10 dpdklab
2023-12-15 2:04 dpdklab
2023-12-15 1:59 dpdklab
2023-12-15 1:58 dpdklab
2023-12-15 1:52 dpdklab
2023-12-15 1:52 dpdklab
2023-12-15 1:45 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=657bb1e5.170a0220.45221.6becSMTPIN_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).