From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153510 [PATCH] app/testpmd: fix random flow item token
Date: Mon, 19 May 2025 00:16:03 -0700 (PDT) [thread overview]
Message-ID: <682adab3.050a0220.214c7f.e4cfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250519063045.394353-1-getelson@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/153510
_Performance Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, May 19 2025 06:30:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6
153510 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#226591
Test environment and result as below:
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.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -1.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33204/
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:[~2025-05-19 7:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250519063045.394353-1-getelson@nvidia.com>
2025-05-19 5:57 ` qemudev
2025-05-19 6:01 ` qemudev
2025-05-19 6:31 ` checkpatch
2025-05-19 7:15 ` dpdklab
2025-05-19 7:16 ` dpdklab [this message]
2025-05-19 7:22 ` 0-day Robot
2025-05-19 7:26 ` dpdklab
2025-05-19 7:27 ` dpdklab
2025-05-19 7:29 ` dpdklab
2025-05-19 7:33 ` dpdklab
2025-05-19 7:36 ` dpdklab
2025-05-19 7:40 ` dpdklab
2025-05-19 7:42 ` |PENDING| " dpdklab
2025-05-19 7:47 ` dpdklab
2025-05-19 7:49 ` |SUCCESS| " dpdklab
2025-05-19 8:02 ` |PENDING| " dpdklab
2025-05-19 8:23 ` dpdklab
2025-05-19 9:01 ` |WARNING| " dpdklab
2025-05-19 9:30 ` |SUCCESS| " dpdklab
2025-05-19 9:33 ` dpdklab
2025-05-19 9:43 ` dpdklab
2025-05-19 10:09 ` dpdklab
2025-05-19 10:21 ` 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=682adab3.050a0220.214c7f.e4cfSMTPIN_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).