From: dpdklab@iol.unh.edu
To: Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw95880 [PATCH] [v2] net/iavf: fix wrong bandwidth unit in TM capability querying
Date: Sat, 17 Jul 2021 10:12:13 -0400 (EDT) [thread overview]
Message-ID: <20210717141213.48DAD88E63@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2967 bytes --]
Test-Label: iol-intel-Performance
Test-Status: FAILURE
http://dpdk.org/patch/95880
_Performance Testing issues_
Submitter: Ting Xu <ting.xu@intel.com>
Date: Thursday, July 15 2021 10:36:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a95bbb72623c310df4d0c8ad45c2ee06f538e01b
95880 --> performance testing fail
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 6.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -2.9% |
+------------+---------+----------+-------------+------------------------------+
| 1 | 2 | 512 | 64 | -3.0% |
+------------+---------+----------+-------------+------------------------------+
| 1 | 2 | 2048 | 64 | -2.4% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 2/4
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -5.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -19.1% |
+------------+---------+----------+-------------+------------------------------+
| 1 | 2 | 512 | 64 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1 | 2 | 2048 | 64 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17837/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-07-17 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 14:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-17 0:16 dpdklab
2021-07-16 23:59 dpdklab
2021-07-15 16:43 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=20210717141213.48DAD88E63@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--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).