From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125254 [PATCH] config/arm: enable rcpc feature on neoverse n1
Date: Mon, 20 Mar 2023 04:32:34 +0000 (UTC) [thread overview]
Message-ID: <20230320043234.A032860214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125254
_Performance Testing PASS_
Submitter: Joyce Kong <joyce.kong@arm.com>
Date: Monday, March 20 2023 03:26:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:56de01c119381f82baef819184a8dba36ea9c333
125254 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25792/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-20 4:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 4:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 13:21 dpdklab
2023-03-22 12:16 dpdklab
2023-03-22 11:25 dpdklab
2023-03-22 11:25 dpdklab
2023-03-20 19:31 dpdklab
2023-03-20 18:28 dpdklab
2023-03-20 17:19 dpdklab
2023-03-20 7:51 dpdklab
2023-03-20 6:13 dpdklab
2023-03-20 6:02 dpdklab
2023-03-20 5:32 dpdklab
2023-03-20 5:21 dpdklab
2023-03-20 4:58 dpdklab
2023-03-20 4:51 dpdklab
2023-03-20 4:48 dpdklab
2023-03-20 4:47 dpdklab
2023-03-20 4:46 dpdklab
2023-03-20 4:43 dpdklab
2023-03-20 4:40 dpdklab
2023-03-20 4:38 dpdklab
2023-03-20 4:34 dpdklab
2023-03-20 4:29 dpdklab
2023-03-20 4:28 dpdklab
2023-03-20 4:26 dpdklab
2023-03-20 4:24 dpdklab
2023-03-20 4:18 dpdklab
2023-03-20 4:17 dpdklab
2023-03-20 4:16 dpdklab
2023-03-20 4:15 dpdklab
2023-03-20 4:13 dpdklab
2023-03-20 4:07 dpdklab
2023-03-20 4:02 dpdklab
[not found] <20230320032655.2119718-1-joyce.kong@arm.com>
2023-03-20 3:16 ` qemudev
2023-03-20 3:20 ` qemudev
2023-03-20 3:28 ` checkpatch
2023-03-20 5:39 ` 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=20230320043234.A032860214@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).