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| pw138662 [PATCH] [v2] net/mlx5/hws: fix port ID for root t
Date: Sat, 23 Mar 2024 05:23:02 -0700 (PDT)	[thread overview]
Message-ID: <65fec9a6.6b0a0220.8f2b8.9901SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321144811.1574579-1-kliteyn@nvidia.com>

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138662

_Performance Testing PASS_

Submitter: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date: Thursday, March 21 2024 14:48:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138662 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

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

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | -0.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.9%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.5%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-23 12:23 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321144811.1574579-1-kliteyn@nvidia.com>
2024-03-21 14:26 ` |SUCCESS| pw138662 [PATCH v2] net/mlx5/hws: fix port ID for root table qemudev
2024-03-21 14:30 ` qemudev
2024-03-21 14:49 ` checkpatch
2024-03-21 16:05 ` 0-day Robot
2024-03-21 20:03 ` |SUCCESS| pw138662 [PATCH] [v2] net/mlx5/hws: fix port ID for root t dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:12 ` dpdklab
2024-03-21 20:12 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:14 ` dpdklab
2024-03-21 20:15 ` dpdklab
2024-03-21 20:15 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:35 ` dpdklab
2024-03-21 20:38 ` dpdklab
2024-03-21 20:38 ` dpdklab
2024-03-21 20:39 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:41 ` dpdklab
2024-03-21 20:41 ` dpdklab
2024-03-21 20:42 ` dpdklab
2024-03-21 20:43 ` dpdklab
2024-03-21 20:43 ` dpdklab
2024-03-21 20:49 ` dpdklab
2024-03-21 20:49 ` dpdklab
2024-03-21 20:50 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:53 ` dpdklab
2024-03-21 20:56 ` dpdklab
2024-03-21 20:58 ` dpdklab
2024-03-21 20:58 ` dpdklab
2024-03-21 20:59 ` dpdklab
2024-03-21 20:59 ` dpdklab
2024-03-21 21:00 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:03 ` dpdklab
2024-03-21 21:04 ` dpdklab
2024-03-21 21:06 ` dpdklab
2024-03-21 21:18 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-21 21:21 ` dpdklab
2024-03-21 21:22 ` dpdklab
2024-03-21 21:39 ` dpdklab
2024-03-21 21:40 ` dpdklab
2024-03-21 21:40 ` dpdklab
2024-03-21 21:41 ` dpdklab
2024-03-21 21:43 ` dpdklab
2024-03-21 21:43 ` dpdklab
2024-03-21 21:44 ` dpdklab
2024-03-21 21:44 ` dpdklab
2024-03-21 21:46 ` dpdklab
2024-03-21 21:49 ` dpdklab
2024-03-21 21:49 ` dpdklab
2024-03-21 21:50 ` dpdklab
2024-03-21 21:58 ` dpdklab
2024-03-21 21:58 ` dpdklab
2024-03-21 21:59 ` dpdklab
2024-03-21 21:59 ` dpdklab
2024-03-21 22:01 ` dpdklab
2024-03-21 22:04 ` dpdklab
2024-03-21 22:05 ` dpdklab
2024-03-21 22:10 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-22  2:59 ` dpdklab
2024-03-23 12:23 ` dpdklab [this message]
2024-03-23 12:59 ` 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=65fec9a6.6b0a0220.8f2b8.9901SMTPIN_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).