From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw93343 [PATCH] event/dlb2: fix extraction of HW scheduling type
Date: Fri, 21 May 2021 02:12:13 -0400 (EDT) [thread overview]
Message-ID: <20210521061213.4BFFB88E70@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2850 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/93343
_Performance Testing PASS_
Submitter: Timothy McDaniel <timothy.mcdaniel@intel.com>
Date: Thursday, May 20 2021 16:11:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1aee2359457b58c42ce9224a4705a61d6bbc31f8
93343 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.00162% |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.41784% |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.26462% |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.39966% |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.28806% |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.04692% |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.39863% |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.1002% |
+------------+---------+-------------------------------------+
| 256 | 256 | -1.52581% |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.10272% |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.20077% |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.02461% |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-05-21 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 6:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 21:22 dpdklab
2021-05-21 21:02 dpdklab
2021-05-21 7:03 dpdklab
2021-05-21 6:51 dpdklab
2021-05-21 5:59 dpdklab
2021-05-21 5:20 dpdklab
2021-05-20 19:16 dpdklab
2021-05-20 17:36 dpdklab
2021-05-20 17:32 dpdklab
2021-05-20 17:26 dpdklab
[not found] <1621527103-5051-1-git-send-email-timothy.mcdaniel@intel.com>
2021-05-20 16:17 ` checkpatch
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=20210521061213.4BFFB88E70@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).