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| pw84445 [PATCH] net/mlx5: fix mbufs overflow in vectorized MPRQ
Date: Sat, 21 Nov 2020 03:52:08 -0500 (EST)	[thread overview]
Message-ID: <20201121085208.5777688E61@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Saturday, November 21 2020 03:42:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:aba2af9936b671e1b492f9c044b3e7f4b7e7628b

84445 --> 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.135                              |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.013                              |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.039                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.064                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.014                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.017                               |
+------------+---------+-------------------------------------+

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.105                              |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.052                              |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.008                              |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.020                               |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.002                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.002                              |
+------------+---------+-------------------------------------+

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.145                               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.149                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.061                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.018                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.013                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.017                              |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-11-21  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21  8:52 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-21  4:49 dpdklab
2020-11-21  4:39 dpdklab
2020-11-21  4:31 dpdklab
2020-11-21  4:25 dpdklab
     [not found] <20201121034239.13404-1-akozyrev@nvidia.com>
2020-11-21  3:43 ` 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=20201121085208.5777688E61@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).