From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@mellanox.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw64109 [PATCH] [v5] app/test: fix build when ring PMD is disabled
Date: Mon, 23 Dec 2019 02:54:28 -0500 (EST) [thread overview]
Message-ID: <20191223075428.B713D60539@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/64109
_Performance Testing PASS_
Submitter: Reshma Pattan <reshma.pattan@intel.com>
Date: Monday, December 23 2019 06:53:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2e088e6f94b773233c06440763c1be43d0d705b3
64109 --> performance testing pass
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: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.013 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.229 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.004 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.024 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.004 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0 |
+------------+---------+-------------------------------------+
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.063 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.130 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.030 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.006 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.006 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.003 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/9011/
UNH-IOL DPDK Community Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2019-12-23 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 7:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-23 7:36 dpdklab
2019-12-23 7:30 dpdklab
2019-12-23 7:30 dpdklab
[not found] <20191223065305.18434-1-reshma.pattan@intel.com>
2019-12-23 6:54 ` [dpdk-test-report] |SUCCESS| pw64109 [PATCH v5] " 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=20191223075428.B713D60539@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.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).