From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133843 [PATCH] [24.03] build: track mandatory rather tha
Date: Fri, 03 Nov 2023 10:45:44 -0700 (PDT) [thread overview]
Message-ID: <654531c8.050a0220.83baf.58e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/133843
_Performance Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, November 03 2023 16:28:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e9555aad006a739de9ae2a14a94128931634eea0
133843 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28226/
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-03 17:45 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:45 dpdklab [this message]
2023-11-03 17:46 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:48 dpdklab
2023-11-03 17:48 dpdklab
2023-11-03 17:48 dpdklab
2023-11-03 17:49 dpdklab
2023-11-03 17:49 dpdklab
2023-11-03 17:49 dpdklab
2023-11-03 17:49 dpdklab
2023-11-03 17:50 dpdklab
2023-11-03 17:52 dpdklab
2023-11-03 17:53 dpdklab
2023-11-03 17:53 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:54 dpdklab
2023-11-03 17:55 dpdklab
2023-11-03 17:55 dpdklab
2023-11-03 17:55 dpdklab
2023-11-03 17:55 dpdklab
2023-11-03 17:55 dpdklab
2023-11-03 17:56 dpdklab
2023-11-03 17:57 dpdklab
2023-11-03 17:58 dpdklab
2023-11-03 17:58 dpdklab
2023-11-03 17:58 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:07 dpdklab
2023-11-03 18:08 dpdklab
2023-11-03 18:08 dpdklab
2023-11-03 18:08 dpdklab
2023-11-03 18:35 dpdklab
2023-11-03 18:45 dpdklab
2023-11-03 18:46 dpdklab
2023-11-03 18:50 dpdklab
2023-11-03 19:10 dpdklab
2023-11-03 19:38 dpdklab
2023-11-03 19:38 dpdklab
2023-11-03 20:17 dpdklab
2023-11-03 20:26 dpdklab
2023-11-03 20:49 dpdklab
2023-11-03 21:19 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=654531c8.050a0220.83baf.58e7SMTPIN_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).