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@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw96417-96419 [PATCH] [2/2] vhost: notice Vhost ops struct renaming
Date: Fri, 30 Jul 2021 11:33:35 -0400 (EDT)	[thread overview]
Message-ID: <20210730153335.E72AD88E71@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, July 29 2021 14:42:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:02e077f35dbc9821dfcb32714ad1096a3ee58d08

96417-96419 --> performance testing pass

Test environment and result as below:

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | -0.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | 1.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-07-30 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 15:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-30 15:16 dpdklab
2021-07-30 13:10 dpdklab
2021-07-29 21:10 dpdklab
2021-07-29 16:34 dpdklab
2021-07-29 16:13 dpdklab

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=20210730153335.E72AD88E71@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=dpdk-test-reports@dpdk.org \
    --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).