From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134469 [PATCH] doc: document basic MSVC build requiremen
Date: Fri, 17 Nov 2023 14:12:23 -0800 (PST) [thread overview]
Message-ID: <6557e547.b00a0220.6e068.75faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/134469
_Performance Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, November 17 2023 21:19:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6d7129a6e93b7cb52efff009b29ef1a0f2cb76b4
134469 --> 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/28412/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-17 22:12 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 22:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-20 15:06 dpdklab
2023-11-17 23:19 dpdklab
2023-11-17 23:04 dpdklab
2023-11-17 22:50 dpdklab
2023-11-17 22:38 dpdklab
2023-11-17 22:38 dpdklab
2023-11-17 22:38 dpdklab
2023-11-17 22:34 dpdklab
2023-11-17 22:32 dpdklab
2023-11-17 22:25 dpdklab
2023-11-17 22:25 dpdklab
2023-11-17 22:25 dpdklab
2023-11-17 22:25 dpdklab
2023-11-17 22:24 dpdklab
2023-11-17 22:17 dpdklab
2023-11-17 22:13 dpdklab
2023-11-17 22:13 dpdklab
2023-11-17 22:13 dpdklab
2023-11-17 22:12 dpdklab
2023-11-17 22:11 dpdklab
2023-11-17 22:11 dpdklab
2023-11-17 22:11 dpdklab
2023-11-17 22:10 dpdklab
2023-11-17 22:10 dpdklab
2023-11-17 22:10 dpdklab
2023-11-17 22:10 dpdklab
2023-11-17 22:10 dpdklab
2023-11-17 22:09 dpdklab
2023-11-17 22:09 dpdklab
2023-11-17 22:09 dpdklab
2023-11-17 22:09 dpdklab
2023-11-17 22:09 dpdklab
2023-11-17 22:08 dpdklab
2023-11-17 22:08 dpdklab
2023-11-17 22:08 dpdklab
2023-11-17 22:08 dpdklab
2023-11-17 22:07 dpdklab
2023-11-17 22:07 dpdklab
2023-11-17 22:06 dpdklab
2023-11-17 22:05 dpdklab
2023-11-17 22:05 dpdklab
2023-11-17 22:05 dpdklab
2023-11-17 22:04 dpdklab
2023-11-17 22:01 dpdklab
2023-11-17 22:00 dpdklab
2023-11-17 22:00 dpdklab
2023-11-17 22:00 dpdklab
2023-11-17 22:00 dpdklab
2023-11-17 21:59 dpdklab
2023-11-17 21:59 dpdklab
2023-11-17 21:59 dpdklab
2023-11-17 21:59 dpdklab
2023-11-17 21:58 dpdklab
2023-11-17 21:58 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=6557e547.b00a0220.6e068.75faSMTPIN_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).