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| pw125593-125614 [PATCH] [v12, 22/22] pipeline: convert RTE_LOGTYPE_PIPELINE to dynamic type
Date: Thu, 30 Mar 2023 15:43:19 +0000 (UTC) [thread overview]
Message-ID: <20230330154319.9352A60123@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125614
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, March 29 2023 23:40:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c682c8991963be243dcc3b7cdc9d6984a1961f4e
125593-125614 --> performance testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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 | 1.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -2.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25887/
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-30 15:43 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 15:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-06 16:29 dpdklab
2023-04-06 16:01 dpdklab
2023-04-06 15:50 dpdklab
2023-04-06 15:49 dpdklab
2023-04-06 15:48 dpdklab
2023-04-06 15:44 dpdklab
2023-04-06 15:41 dpdklab
2023-04-06 15:36 dpdklab
2023-04-06 15:28 dpdklab
2023-04-06 15:25 dpdklab
2023-04-06 15:21 dpdklab
2023-04-06 15:21 dpdklab
2023-04-06 15:14 dpdklab
2023-04-06 15:13 dpdklab
2023-04-06 15:12 dpdklab
2023-04-06 15:10 dpdklab
2023-04-06 15:10 dpdklab
2023-04-06 15:05 dpdklab
2023-04-06 15:02 dpdklab
2023-04-06 14:53 dpdklab
2023-03-30 17:45 dpdklab
2023-03-30 17:12 dpdklab
2023-03-30 16:46 dpdklab
2023-03-30 16:35 dpdklab
2023-03-30 16:23 dpdklab
2023-03-30 16:23 dpdklab
2023-03-30 16:22 dpdklab
2023-03-30 16:10 dpdklab
2023-03-30 16:09 dpdklab
2023-03-30 16:03 dpdklab
2023-03-30 15:57 dpdklab
2023-03-30 15:52 dpdklab
2023-03-30 15:47 dpdklab
2023-03-30 15:46 dpdklab
2023-03-30 15:45 dpdklab
2023-03-30 15:45 dpdklab
2023-03-30 15:44 dpdklab
2023-03-30 15:44 dpdklab
2023-03-30 15:44 dpdklab
2023-03-30 15:40 dpdklab
2023-03-30 15:37 dpdklab
2023-03-30 15:33 dpdklab
2023-03-30 15:33 dpdklab
2023-03-30 15:30 dpdklab
2023-03-30 15:28 dpdklab
2023-03-30 15:28 dpdklab
2023-03-30 15:25 dpdklab
2023-03-30 15:24 dpdklab
2023-03-30 15:24 dpdklab
2023-03-30 15:21 dpdklab
2023-03-30 15:20 dpdklab
2023-03-30 15:17 dpdklab
2023-03-30 15:12 dpdklab
2023-03-30 15:12 dpdklab
2023-03-30 15:09 dpdklab
2023-03-30 4:16 dpdklab
2023-03-30 4:16 dpdklab
2023-03-30 4:00 dpdklab
2023-03-30 3:59 dpdklab
2023-03-30 3:26 dpdklab
2023-03-30 3:26 dpdklab
2023-03-30 3:21 dpdklab
2023-03-30 3:19 dpdklab
2023-03-30 3:14 dpdklab
2023-03-30 3:09 dpdklab
2023-03-30 3:07 dpdklab
2023-03-30 3:06 dpdklab
2023-03-30 3:04 dpdklab
2023-03-30 3:01 dpdklab
2023-03-30 3:00 dpdklab
2023-03-30 2:59 dpdklab
2023-03-30 2:57 dpdklab
2023-03-30 2:55 dpdklab
2023-03-30 2:55 dpdklab
2023-03-30 2:55 dpdklab
2023-03-30 2:49 dpdklab
2023-03-30 2:48 dpdklab
2023-03-30 2:48 dpdklab
[not found] <20230329234049.11071-23-stephen@networkplumber.org>
2023-03-29 23:32 ` |SUCCESS| pw125593-125614 [PATCH v12 " qemudev
2023-03-29 23:36 ` qemudev
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=20230330154319.9352A60123@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).