From: dpdklab@iol.unh.edu
To: Erez Scop <erezsc@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ali Alnubani <alialnu@mellanox.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw59331 [PATCH] net/mlx5: fix transmit doorbell register write barrier
Date: Wed, 18 Sep 2019 04:27:32 -0400 (EDT) [thread overview]
Message-ID: <20190918082732.EC13E1D1@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3922 bytes --]
Test-Label: mellanox-Performance
Test-Status: FAILURE
http://dpdk.org/patch/59331
_Performance Testing issues_
Submitter: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Date: Wednesday, September 18 2019 06:54:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:73afc9df00d8ba4ff58d4a7a86691ca10520d462
59331 --> performance testing fail
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -1.368 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.767 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.881 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.021 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.021 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.007 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.775 |
+------------+---------+-------------------------------------+
| 128 | 256 | -1.192 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.026 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.005 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.013 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.009 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 2/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -3.919 |
+------------+---------+-------------------------------------+
| 128 | 256 | -1.084 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.538 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.006 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.042 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.019 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/7525/
UNH-IOL DPDK Performance Test Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2019-09-18 8:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190918082732.EC13E1D1@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=erezsc@mellanox.com \
--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).