automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw58970 [PATCH] [v4] net/i40e: validate all messages from VF
Date: Mon,  9 Sep 2019 05:41:58 -0400 (EDT)	[thread overview]
Message-ID: <20190909094158.63C2F6D557@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 3899 bytes --]

Test-Label: mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/58970

_Performance Testing PASS_

Submitter: None <alvinx.zhang@intel.com>
Date: Monday, September 09 2019 15:11:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2afa82430f0a60824fa4e0bf2a23191a5bc32a6d

58970 --> 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.203                              |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.384                               |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.014                              |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.044                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.026                               |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.005                               |
+------------+---------+-------------------------------------+

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.153                               |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.030                              |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.032                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.004                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.004                               |
+------------+---------+-------------------------------------+
| 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: 0/6

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 256     | -0.122                              |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.006                              |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.025                              |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.012                               |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.059                               |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.019                               |
+------------+---------+-------------------------------------+

https://lab.dpdk.org/results/dashboard/patchsets/7423/

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-09  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  9:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-09  9:15 dpdklab
2019-09-09  9:12 dpdklab
2019-09-09  9:10 dpdklab
2019-09-09  9:08 dpdklab
     [not found] <20190909151106.70803-1-alvinx.zhang@intel.com>
2019-09-09  6:22 ` [dpdk-test-report] |SUCCESS| pw58970 [PATCH v4] " 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=20190909094158.63C2F6D557@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).