automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141981 [PATCH] net/netvsc: fix mtu_set in netvsc devices
Date: Sun, 30 Jun 2024 07:01:28 -0700 (PDT)	[thread overview]
Message-ID: <66816538.050a0220.68901.b167SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240628163503.15893-1-askorichenko@netgate.com>

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141981

_Performance Testing PASS_

Submitter: Alexander Skorichenko <askorichenko@netgate.com>
Date: Friday, June 28 2024 16:35:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2

141981 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown
Fail/Total: 0/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -2.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 4.2%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -1.4%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 1.5%                         |
+----------+-------------+---------+------------+------------------------------+

22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 Mbps
Target: Unknown
Fail/Total: 0/4

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 2           | -1.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 2           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.6%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-30 14:01 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240628163503.15893-1-askorichenko@netgate.com>
2024-06-30 12:19 ` qemudev
2024-06-30 12:23 ` qemudev
2024-06-30 12:47 ` checkpatch
2024-06-30 13:57 ` dpdklab
2024-06-30 13:59 ` dpdklab
2024-06-30 14:01 ` dpdklab [this message]
2024-06-30 14:02 ` |PENDING| " dpdklab
2024-06-30 14:04 ` |SUCCESS| " dpdklab
2024-06-30 14:05 ` dpdklab
2024-06-30 14:06 ` |PENDING| " dpdklab
2024-06-30 14:08 ` dpdklab
2024-06-30 14:10 ` dpdklab
2024-06-30 14:11 ` dpdklab
2024-06-30 14:12 ` dpdklab
2024-06-30 14:13 ` |SUCCESS| " dpdklab
2024-06-30 14:13 ` dpdklab
2024-06-30 14:16 ` dpdklab
2024-06-30 14:18 ` dpdklab
2024-06-30 14:19 ` dpdklab
2024-06-30 14:20 ` dpdklab
2024-06-30 14:24 ` dpdklab
2024-06-30 14:28 ` |PENDING| " dpdklab
2024-06-30 14:42 ` dpdklab
2024-06-30 14:45 ` dpdklab
2024-06-30 14:49 ` |SUCCESS| " dpdklab
2024-06-30 14:53 ` dpdklab
2024-06-30 14:54 ` |PENDING| " dpdklab
2024-06-30 14:57 ` |SUCCESS| " dpdklab
2024-06-30 15:02 ` |PENDING| " dpdklab
2024-06-30 15:04 ` dpdklab
2024-06-30 15:10 ` dpdklab
2024-06-30 15:11 ` dpdklab
2024-06-30 15:13 ` dpdklab
2024-06-30 15:14 ` dpdklab
2024-06-30 15:16 ` |SUCCESS| " dpdklab
2024-06-30 15:17 ` |PENDING| " dpdklab
2024-06-30 15:18 ` dpdklab
2024-06-30 15:21 ` dpdklab
2024-06-30 15:23 ` dpdklab
2024-06-30 15:28 ` dpdklab
2024-06-30 15:28 ` dpdklab
2024-06-30 15:30 ` dpdklab
2024-06-30 15:30 ` dpdklab
2024-06-30 15:32 ` dpdklab
2024-06-30 15:33 ` dpdklab
2024-06-30 15:35 ` dpdklab
2024-06-30 15:35 ` dpdklab
2024-06-30 15:36 ` dpdklab
2024-06-30 15:42 ` dpdklab
2024-06-30 15:43 ` dpdklab
2024-06-30 15:44 ` |SUCCESS| " dpdklab
2024-06-30 15:45 ` |PENDING| " dpdklab
2024-06-30 15:45 ` dpdklab
2024-06-30 15:45 ` dpdklab
2024-06-30 15:49 ` dpdklab
2024-06-30 15:50 ` |SUCCESS| " dpdklab
2024-06-30 15:51 ` |PENDING| " dpdklab
2024-06-30 15:51 ` dpdklab
2024-06-30 15:52 ` dpdklab
2024-06-30 15:52 ` dpdklab
2024-06-30 15:53 ` dpdklab
2024-06-30 15:53 ` dpdklab
2024-06-30 15:53 ` dpdklab
2024-06-30 15:56 ` dpdklab
2024-06-30 15:59 ` dpdklab
2024-06-30 16:00 ` dpdklab
2024-06-30 16:00 ` dpdklab
2024-06-30 16:01 ` dpdklab
2024-06-30 16:03 ` dpdklab
2024-06-30 16:04 ` dpdklab
2024-06-30 16:05 ` dpdklab
2024-06-30 16:05 ` dpdklab
2024-06-30 16:05 ` dpdklab
2024-06-30 16:06 ` dpdklab
2024-06-30 16:09 ` dpdklab
2024-06-30 16:09 ` dpdklab
2024-06-30 16:10 ` dpdklab
2024-06-30 16:11 ` dpdklab
2024-06-30 16:12 ` dpdklab
2024-06-30 16:14 ` dpdklab
2024-06-30 16:14 ` dpdklab
2024-06-30 16:17 ` |SUCCESS| " dpdklab
2024-06-30 16:18 ` |PENDING| " dpdklab
2024-06-30 16:23 ` dpdklab
2024-06-30 16:25 ` |SUCCESS| " dpdklab
2024-06-30 16:35 ` |PENDING| " dpdklab
2024-06-30 16:55 ` dpdklab
2024-06-30 16:59 ` dpdklab
2024-06-30 17:11 ` dpdklab
2024-06-30 17:28 ` dpdklab
2024-06-30 17:34 ` dpdklab
2024-06-30 17:35 ` dpdklab
2024-06-30 17:39 ` dpdklab
2024-06-30 17:41 ` dpdklab
2024-06-30 17:42 ` dpdklab
2024-06-30 17:42 ` dpdklab
2024-06-30 17:44 ` dpdklab
2024-06-30 17:44 ` dpdklab
2024-06-30 17:47 ` dpdklab
2024-06-30 17:49 ` dpdklab
2024-06-30 17:52 ` dpdklab
2024-06-30 17:54 ` dpdklab
2024-06-30 18:00 ` dpdklab
2024-06-30 18:02 ` dpdklab
2024-06-30 18:07 ` dpdklab
2024-06-30 18:12 ` dpdklab
2024-06-30 18:22 ` dpdklab
2024-06-30 18:29 ` dpdklab
2024-06-30 18:30 ` dpdklab
2024-06-30 18:37 ` dpdklab
2024-06-30 18:37 ` dpdklab
2024-06-30 18:40 ` dpdklab
2024-06-30 18:42 ` dpdklab
2024-06-30 18:44 ` dpdklab
2024-06-30 19:09 ` |SUCCESS| " dpdklab
2024-06-30 19:36 ` 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=66816538.050a0220.68901.b167SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).