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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126697 [PATCH] [v2] net/iavf: add devargs to control watchdog
Date: Thu, 04 May 2023 20:01:00 -0700 (PDT)	[thread overview]
Message-ID: <6454716c.050a0220.53937.3df6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, May 05 2023 02:27:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126697 --> performance testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-05  3:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  3:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-05  4:24 dpdklab
2023-05-05  3:54 dpdklab
2023-05-05  3:51 dpdklab
2023-05-05  3:51 dpdklab
2023-05-05  3:43 dpdklab
2023-05-05  3:39 dpdklab
2023-05-05  3:37 dpdklab
2023-05-05  3:30 dpdklab
2023-05-05  3:29 dpdklab
2023-05-05  3:29 dpdklab
2023-05-05  3:27 dpdklab
2023-05-05  3:25 dpdklab
2023-05-05  3:21 dpdklab
2023-05-05  3:21 dpdklab
     [not found] <20230505022717.3702876-1-zhichaox.zeng@intel.com>
2023-05-05  2:16 ` |SUCCESS| pw126697 [PATCH v2] " qemudev
2023-05-05  2:20 ` qemudev
2023-05-05  2:23 ` checkpatch
2023-05-05  3:19 ` 0-day Robot
2023-05-05  3:17 |SUCCESS| pw126697 [PATCH] [v2] " dpdklab
2023-05-05  3:07 dpdklab
2023-05-05  3:05 dpdklab
2023-05-05  3:01 dpdklab
2023-05-05  3:00 dpdklab
2023-05-05  3:00 dpdklab
2023-05-05  3:00 dpdklab
2023-05-05  2:59 dpdklab
2023-05-05  2:59 dpdklab
2023-05-05  2:59 dpdklab
2023-05-05  2:57 dpdklab
2023-05-05  2:57 dpdklab
2023-05-05  2:55 dpdklab
2023-05-05  2:53 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=6454716c.050a0220.53937.3df6SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).