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| pw125197 [PATCH] [v2, 1/1] test/mbuf: fix mbuf autotest when mbuf debug is enabled
Date: Thu, 16 Mar 2023 21:35:30 +0000 (UTC) [thread overview]
Message-ID: <20230316213530.79BF26011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125197
_Performance Testing PASS_
Submitter: Pavel Ivashchenko <pivashchenko@nfware.com>
Date: Thursday, March 16 2023 19:14:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8c9bfcb1553d756eb5392a56ac7813b3865c3ec7
125197 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25770/
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-16 21:35 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 21:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-19 13:46 dpdklab
2023-03-19 13:46 dpdklab
2023-03-19 13:44 dpdklab
2023-03-19 13:44 dpdklab
2023-03-19 13:37 dpdklab
2023-03-19 13:31 dpdklab
2023-03-19 13:28 dpdklab
2023-03-19 13:27 dpdklab
2023-03-19 13:22 dpdklab
2023-03-19 13:18 dpdklab
2023-03-19 13:13 dpdklab
2023-03-19 13:11 dpdklab
2023-03-19 13:05 dpdklab
2023-03-19 12:42 dpdklab
2023-03-19 12:42 dpdklab
2023-03-19 12:39 dpdklab
2023-03-19 12:33 dpdklab
2023-03-19 12:33 dpdklab
2023-03-19 12:26 dpdklab
2023-03-19 12:24 dpdklab
2023-03-19 12:24 dpdklab
2023-03-19 12:17 dpdklab
2023-03-19 12:17 dpdklab
2023-03-19 12:07 dpdklab
2023-03-19 12:06 dpdklab
2023-03-19 12:01 dpdklab
2023-03-19 11:57 dpdklab
2023-03-19 11:12 dpdklab
2023-03-19 3:51 dpdklab
2023-03-19 3:04 dpdklab
2023-03-19 1:20 dpdklab
2023-03-18 22:50 dpdklab
2023-03-17 16:29 dpdklab
2023-03-17 2:41 dpdklab
2023-03-17 2:30 dpdklab
2023-03-17 2:29 dpdklab
2023-03-17 2:04 dpdklab
2023-03-17 0:48 dpdklab
2023-03-17 0:27 dpdklab
2023-03-17 0:14 dpdklab
2023-03-17 0:02 dpdklab
2023-03-16 23:12 dpdklab
2023-03-16 22:56 dpdklab
2023-03-16 22:43 dpdklab
2023-03-16 22:26 dpdklab
2023-03-16 22:11 dpdklab
2023-03-16 22:05 dpdklab
2023-03-16 22:01 dpdklab
2023-03-16 21:46 dpdklab
2023-03-16 21:41 dpdklab
2023-03-16 21:37 dpdklab
2023-03-16 21:28 dpdklab
2023-03-16 21:28 dpdklab
2023-03-16 21:23 dpdklab
2023-03-16 21:21 dpdklab
2023-03-16 21:15 dpdklab
2023-03-16 21:14 dpdklab
2023-03-16 21:02 dpdklab
2023-03-16 20:52 dpdklab
2023-03-16 20:51 dpdklab
2023-03-16 20:44 dpdklab
2023-03-16 20:38 dpdklab
[not found] <20230316191456.54066-1-pivashchenko@nfware.com>
2023-03-16 19:05 ` |SUCCESS| pw125197 [PATCH v2 " qemudev
2023-03-16 19:09 ` qemudev
2023-03-16 21:19 ` 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=20230316213530.79BF26011D@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).