From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147882-147885 [PATCH] [v4,4/4] net/nfp: add LED support
Date: Sun, 03 Nov 2024 18:19:20 -0800 (PST) [thread overview]
Message-ID: <67282f28.630a0220.3c49c9.a6faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241104013442.308780-5-chaoyong.he@corigine.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/147885
_Performance Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, November 04 2024 01:34:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1bbb60642423bb0c3f638f7d63a9e6dd6863785e
147882-147885 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#193843
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
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.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 1.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31809/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-11-04 2:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241104013442.308780-5-chaoyong.he@corigine.com>
2024-11-04 1:05 ` |SUCCESS| pw147882-147885 [PATCH v4 4/4] " qemudev
2024-11-04 1:09 ` qemudev
2024-11-04 1:36 ` |SUCCESS| pw147885 " checkpatch
2024-11-04 2:08 ` |PENDING| pw147882-147885 [PATCH] [v4,4/4] " dpdklab
2024-11-04 2:09 ` dpdklab
2024-11-04 2:14 ` dpdklab
2024-11-04 2:16 ` dpdklab
2024-11-04 2:19 ` dpdklab [this message]
2024-11-04 2:21 ` |SUCCESS| " dpdklab
2024-11-04 2:21 ` dpdklab
2024-11-04 2:28 ` dpdklab
2024-11-04 2:29 ` dpdklab
2024-11-04 2:32 ` dpdklab
2024-11-04 2:34 ` dpdklab
2024-11-04 2:35 ` dpdklab
2024-11-04 2:37 ` dpdklab
2024-11-04 2:54 ` dpdklab
2024-11-04 2:55 ` dpdklab
2024-11-04 2:56 ` dpdklab
2024-11-04 4:05 ` 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=67282f28.630a0220.3c49c9.a6faSMTPIN_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).