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| pw124573 [PATCH] [v1] ethdev: remove bitfields from trace
Date: Tue, 28 Feb 2023 16:24:01 +0000 (UTC) [thread overview]
Message-ID: <20230228162401.C3038601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124573
_Performance Testing PASS_
Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Tuesday, February 28 2023 15:55:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124573 --> 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 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.8% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25563/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-28 16:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 16:24 dpdklab [this message]
[not found] <20230228155516.2403535-1-adwivedi@marvell.com>
2023-02-28 15:56 ` |SUCCESS| pw124573 [PATCH v1] " checkpatch
2023-02-28 17:39 ` 0-day Robot
2023-03-01 8:14 ` qemudev
2023-03-01 8:15 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 21:45 |SUCCESS| pw124573 [PATCH] [v1] " dpdklab
2023-02-28 21:45 dpdklab
2023-02-28 21:32 dpdklab
2023-02-28 21:31 dpdklab
2023-02-28 21:27 dpdklab
2023-02-28 21:15 dpdklab
2023-02-28 21:11 dpdklab
2023-02-28 21:11 dpdklab
2023-02-28 21:07 dpdklab
2023-02-28 21:07 dpdklab
2023-02-28 20:58 dpdklab
2023-02-28 20:56 dpdklab
2023-02-28 20:36 dpdklab
2023-02-28 20:32 dpdklab
2023-02-28 20:08 dpdklab
2023-02-28 20:05 dpdklab
2023-02-28 19:07 dpdklab
2023-02-28 18:12 dpdklab
2023-02-28 18:12 dpdklab
2023-02-28 18:09 dpdklab
2023-02-28 18:02 dpdklab
2023-02-28 18:00 dpdklab
2023-02-28 17:58 dpdklab
2023-02-28 17:57 dpdklab
2023-02-28 17:55 dpdklab
2023-02-28 17:48 dpdklab
2023-02-28 17:47 dpdklab
2023-02-28 17:45 dpdklab
2023-02-28 17:39 dpdklab
2023-02-28 17:38 dpdklab
2023-02-28 17:34 dpdklab
2023-02-28 17:26 dpdklab
2023-02-28 17:17 dpdklab
2023-02-28 17:15 dpdklab
2023-02-28 17:02 dpdklab
2023-02-28 16:40 dpdklab
2023-02-28 16:36 dpdklab
2023-02-28 16:33 dpdklab
2023-02-28 16:33 dpdklab
2023-02-28 16:31 dpdklab
2023-02-28 16:27 dpdklab
2023-02-28 16:26 dpdklab
2023-02-28 16:25 dpdklab
2023-02-28 16: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=20230228162401.C3038601B1@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).