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| pw147574-147575 [PATCH] [v2,2/2] net/cnxk: support rte flo
Date: Wed, 30 Oct 2024 15:26:15 -0700 (PDT)	[thread overview]
Message-ID: <6722b287.a70a0220.1a426a.0eb4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241029073106.2620920-2-psatheesh@marvell.com>

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

_Performance Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Tuesday, October 29 2024 07:31:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:30776b2d8db803538e318baaaef4dcc8711a5745

147574-147575 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#192642

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.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

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-30 22:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241029073106.2620920-2-psatheesh@marvell.com>
2024-10-29  7:01 ` |SUCCESS| pw147574-147575 [PATCH v2 2/2] net/cnxk: support rte flow on cn20k qemudev
2024-10-29  7:05 ` qemudev
2024-10-29  7:33 ` |WARNING| pw147575 " checkpatch
2024-10-29  8:24 ` |SUCCESS| pw147575 [dpdk-dev] " 0-day Robot
2024-10-30  7:24 ` |SUCCESS| pw147574-147575 [PATCH] [v2,2/2] net/cnxk: support rte flo dpdklab
2024-10-30 11:46 ` dpdklab
2024-10-30 12:27 ` dpdklab
2024-10-30 13:54 ` dpdklab
2024-10-30 14:34 ` dpdklab
2024-10-30 16:09 ` |PENDING| " dpdklab
2024-10-30 16:37 ` |SUCCESS| " dpdklab
2024-10-30 16:41 ` |PENDING| " dpdklab
2024-10-30 20:13 ` dpdklab
2024-10-30 20:16 ` dpdklab
2024-10-30 21:06 ` |SUCCESS| " dpdklab
2024-10-30 21:59 ` dpdklab
2024-10-30 22:26 ` dpdklab [this message]
2024-10-30 23:02 ` dpdklab
2024-10-31  0:22 ` 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=6722b287.a70a0220.1a426a.0eb4SMTPIN_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).