From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129450-129452 [PATCH] [3/3] app/testpmd: fix meter mark
Date: Wed, 12 Jul 2023 14:04:56 -0700 (PDT) [thread overview]
Message-ID: <64af1578.020a0220.d6b84.44b4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129452
_Performance Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Tuesday, July 11 2023 15:20:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24
129450-129452 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
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.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27042/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-12 21:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 21:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 21:36 dpdklab
2023-07-12 21:32 dpdklab
2023-07-12 21:17 dpdklab
2023-07-12 21:09 dpdklab
2023-07-12 19:29 dpdklab
2023-07-12 9:59 dpdklab
2023-07-12 9:58 dpdklab
2023-07-12 7:58 dpdklab
2023-07-12 7:17 dpdklab
2023-07-12 5:47 dpdklab
2023-07-12 5:38 dpdklab
2023-07-12 5:37 dpdklab
2023-07-12 5:32 dpdklab
2023-07-12 5:32 dpdklab
2023-07-12 5:30 dpdklab
2023-07-12 5:27 dpdklab
2023-07-12 5:27 dpdklab
2023-07-12 5:23 dpdklab
2023-07-12 5:05 dpdklab
2023-07-12 4:53 dpdklab
2023-07-12 4:36 dpdklab
2023-07-12 4:35 dpdklab
2023-07-12 4:35 dpdklab
2023-07-12 4:34 dpdklab
2023-07-12 4:34 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=64af1578.020a0220.d6b84.44b4SMTPIN_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).