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| pw57821 [PATCH] [v2, 1/3] lib/eal: fix vfio unmap that fails unexpectedly
Date: Thu, 22 Aug 2019 15:07:30 -0400 (EDT) [thread overview]
Message-ID: <20190822190730.E81744F9@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3937 bytes --]
Test-Label: mellanox-Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/57821
_Performance Testing issues_
Submitter: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>
Date: Thursday, August 22 2019 11:53:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e7fd5a3bbe5636e93a66fd5086f182756624c97a
57821 --> 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 | -0.479 |
+------------+---------+-------------------------------------+
| 128 | 256 | -1.297 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.638 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.008 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.003 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.001 |
+------------+---------+-------------------------------------+
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: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.437 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.211 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.093 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.015 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.007 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0 |
+------------+---------+-------------------------------------+
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: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.071 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.207 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.145 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.013 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.013 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.034 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/7208/
UNH-IOL DPDK Performance Test Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2019-08-22 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 19:07 dpdklab [this message]
2019-08-25 18:30 dpdklab
2019-08-26 16:13 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=20190822190730.E81744F9@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).