From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147512 [PATCH] config/arm: fix warning for native build
Date: Fri, 01 Nov 2024 16:44:46 -0700 (PDT) [thread overview]
Message-ID: <672567ee.170a0220.369f51.67e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241028131047.3036831-1-david.marchand@redhat.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/147512
_Performance Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Monday, October 28 2024 13:10:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a682d65f8dbe1e8be9cc2425095827e18c700e3
147512 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#193392
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.5% |
+------------+---------+----------+-------------+------------------------------+
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 | -1.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -2.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 4.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31721/
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-01 23:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241028131047.3036831-1-david.marchand@redhat.com>
2024-10-28 12:46 ` |SUCCESS| pw147512 [PATCH] config/arm: fix warning for native build with meson >= 0.55 qemudev
2024-10-28 12:50 ` qemudev
2024-10-28 13:11 ` checkpatch
2024-10-28 14:06 ` 0-day Robot
2024-10-31 19:26 ` |SUCCESS| pw147512 [PATCH] config/arm: fix warning for native build dpdklab
2024-10-31 19:35 ` |PENDING| " dpdklab
2024-10-31 21:16 ` dpdklab
2024-10-31 22:43 ` |SUCCESS| " dpdklab
2024-10-31 22:57 ` dpdklab
2024-10-31 23:40 ` dpdklab
2024-10-31 23:50 ` dpdklab
2024-10-31 23:50 ` dpdklab
2024-10-31 23:51 ` dpdklab
2024-11-01 0:11 ` dpdklab
2024-11-01 7:09 ` dpdklab
2024-11-01 17:08 ` dpdklab
2024-11-01 23:44 ` dpdklab [this message]
2024-11-02 0:20 ` 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=672567ee.170a0220.369f51.67e1SMTPIN_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).