automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw86733 [PATCH] common/sfc_efx/base: apply mask to value on match field set
Date: Wed, 20 Jan 2021 03:01:37 -0500 (EST)	[thread overview]
Message-ID: <20210120080137.98B194DC@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: Sunday, January 17 2021 22:21:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e03d2c3c705e40281bda2f11a947f4d3d5e062e6

86733 --> performance testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: 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.157                               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.109                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.024                               |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.020                               |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.040                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.007                              |
+------------+---------+-------------------------------------+

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: 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.059                               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.246                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.270                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.028                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.005                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.001                              |
+------------+---------+-------------------------------------+

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: 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.209                              |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.347                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.306                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.071                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.021                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.010                               |
+------------+---------+-------------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15238/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2021-01-20  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  8:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-20 22:11 dpdklab
2021-01-20 21:46 dpdklab
2021-01-20  9:18 dpdklab
2021-01-18  1:08 dpdklab
2021-01-18  0:19 dpdklab
2021-01-18  0:04 dpdklab
2021-01-17 23:48 dpdklab
2021-01-17 23:38 dpdklab
2021-01-17 23:28 dpdklab
2021-01-17 23:25 dpdklab
2021-01-17 23:19 dpdklab
     [not found] <20210117222112.26305-1-ivan.malov@oktetlabs.ru>
2021-01-17 22:21 ` 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=20210120080137.98B194DC@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.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).