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| pw93192 [PATCH] [v2] net/iavf: fix wrong Tx context descriptor
Date: Thu, 13 May 2021 16:26:02 -0400 (EDT)	[thread overview]
Message-ID: <20210513202602.A8C2B8904B@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Wednesday, May 12 2021 08:10:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:86ff0663639417f9d25907d09343a5c231e32a51

93192 --> 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.13581%                           |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.0589%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.31954%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.86149%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.05931%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.17595%                            |
+------------+---------+-------------------------------------+

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.11703%                            |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.12879%                           |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.14268%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.06923%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.02088%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.0%                                |
+------------+---------+-------------------------------------+

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.20356%                            |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.12785%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | -1.03537%                           |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.10272%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.01673%                            |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.19685%                           |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-05-13 20:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 20:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-14 10:49 dpdklab
2021-05-14  8:34 dpdklab
2021-05-14  8:08 dpdklab
2021-05-14  7:53 dpdklab
2021-05-14  7:29 dpdklab
2021-05-14  5:14 dpdklab
2021-05-14  4:49 dpdklab
2021-05-14  4:34 dpdklab
2021-05-13 21:18 dpdklab
2021-05-13 21:06 dpdklab
2021-05-13 20:13 dpdklab
2021-05-13 19:32 dpdklab
2021-05-13 18:38 dpdklab
2021-05-13 18:26 dpdklab
2021-05-13 18:13 dpdklab
2021-05-12 11:45 dpdklab
2021-05-12 10:55 dpdklab
2021-05-12 10:44 dpdklab
2021-05-12 10:33 dpdklab
2021-05-12 10:26 dpdklab
2021-05-12 10:15 dpdklab
     [not found] <20210512081014.103374-1-beilei.xing@intel.com>
2021-05-12  8:24 ` [dpdk-test-report] |SUCCESS| pw93192 [PATCH v2] " 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=20210513202602.A8C2B8904B@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).