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| pw144401-144403 [PATCH] [V2,3/3] net/mlx5/hws: print CQE e
Date: Tue, 24 Sep 2024 05:11:42 -0700 (PDT)	[thread overview]
Message-ID: <66f2ac7e.050a0220.246cce.1b8dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240924055938.48374-4-gavinl@nvidia.com>

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

_Performance Testing PASS_

Submitter: Minggang Li(Gavin) <gavinl@nvidia.com>
Date: Tuesday, September 24 2024 05:59:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cba452c8a72c22c0f60fa6313f79c825afcabe07

144401-144403 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#183132

Test environment and result as below:

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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-24 12:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240924055938.48374-4-gavinl@nvidia.com>
2024-09-24  5:34 ` |SUCCESS| pw144401-144403 [PATCH V2 3/3] net/mlx5/hws: print CQE error syndrome and more information qemudev
2024-09-24  5:38 ` qemudev
2024-09-24  6:01 ` |WARNING| pw144403 " checkpatch
2024-09-24  7:03 ` |SUCCESS| " 0-day Robot
2024-09-24 12:11 ` dpdklab [this message]
2024-09-24 12:14 ` |SUCCESS| pw144401-144403 [PATCH] [V2,3/3] net/mlx5/hws: print CQE e dpdklab
2024-09-24 12:15 ` dpdklab
2024-09-24 12:27 ` dpdklab
2024-09-24 12:33 ` dpdklab
2024-09-24 12:45 ` dpdklab
2024-09-24 12:48 ` dpdklab
2024-09-24 13:47 ` dpdklab
2024-09-24 13:59 ` dpdklab
2024-09-24 14:04 ` |PENDING| " dpdklab
2024-09-24 14:34 ` dpdklab
2024-09-24 14:35 ` dpdklab
2024-09-24 14:45 ` |SUCCESS| " dpdklab
2024-09-24 15:16 ` dpdklab
2024-09-24 15:24 ` dpdklab
2024-09-24 15:39 ` dpdklab
2024-09-24 15:56 ` dpdklab
2024-09-24 16:03 ` 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=66f2ac7e.050a0220.246cce.1b8dSMTPIN_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).