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| pw147558 [PATCH] net/mlx5: fix shared Rx queue port number
Date: Wed, 30 Oct 2024 22:01:09 -0700 (PDT)	[thread overview]
Message-ID: <67230f15.170a0220.15629f.1cc3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241028175358.2268101-1-akozyrev@nvidia.com>

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

_Performance Testing PASS_

Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Monday, October 28 2024 17:53:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6dad0bb5c8621644beca86ff5f4910a943ba604d

147558 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#192747

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
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.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
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-31  5:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241028175358.2268101-1-akozyrev@nvidia.com>
2024-10-28 17:23 ` |SUCCESS| pw147558 [PATCH] net/mlx5: fix shared Rx queue port number in data path qemudev
2024-10-28 17:27 ` qemudev
2024-10-28 17:56 ` checkpatch
2024-10-28 18:44 ` 0-day Robot
2024-10-30  8:56 ` |SUCCESS| pw147558 [PATCH] net/mlx5: fix shared Rx queue port number dpdklab
2024-10-30 14:58 ` dpdklab
2024-10-30 15:02 ` dpdklab
2024-10-30 15:50 ` dpdklab
2024-10-30 16:03 ` dpdklab
2024-10-30 18:18 ` dpdklab
2024-10-30 20:29 ` |PENDING| " dpdklab
2024-10-30 20:51 ` |SUCCESS| " dpdklab
2024-10-30 20:54 ` |PENDING| " dpdklab
2024-10-31  0:13 ` dpdklab
2024-10-31  0:53 ` |SUCCESS| " dpdklab
2024-10-31  1:33 ` dpdklab
2024-10-31  5:01 ` dpdklab [this message]
2024-10-31  5:31 ` dpdklab
2024-10-31  6:15 ` 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=67230f15.170a0220.15629f.1cc3SMTPIN_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).