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| pw93246 [PATCH] [v1] net/mlx5: fix meter cleaning in stop operation
Date: Sat, 15 May 2021 17:17:55 -0400 (EDT)	[thread overview]
Message-ID: <20210515211755.2730D4E0@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Li Zhang <lizh@nvidia.com>
Date: Thursday, May 13 2021 07:35:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7989b7e7da9be588563c809264c9347a35319969

93246 --> performance testing pass

Test environment and result as below:

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.92767%                            |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.45507%                           |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.10609%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.08521%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.01044%                            |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.01538%                            |
+------------+---------+-------------------------------------+

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.7492%                             |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.27642%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.78272%                           |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.17976%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.11712%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.27067%                           |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-05-15 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 21:17 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-16 19:54 dpdklab
2021-05-16 19:28 dpdklab
2021-05-16 19:05 dpdklab
2021-05-16 16:50 dpdklab
2021-05-15 22:10 dpdklab
2021-05-15 21:58 dpdklab
2021-05-15 21:05 dpdklab
2021-05-15 20:24 dpdklab
2021-05-13  8:06 dpdklab
2021-05-13  8:06 dpdklab
2021-05-13  8:03 dpdklab
2021-05-13  7:52 dpdklab
     [not found] <20210513073552.3213962-1-lizh@nvidia.com>
2021-05-13  7:36 ` [dpdk-test-report] |SUCCESS| pw93246 [PATCH v1] " 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=20210515211755.2730D4E0@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).