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| pw143205-143207 [PATCH] [v4,5/5] node: add error stats for
Date: Mon, 19 Aug 2024 02:03:17 -0700 (PDT)	[thread overview]
Message-ID: <66c30a55.050a0220.9ee41.4352SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240816150926.5789-5-pbhagavatula@marvell.com>

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

_Performance Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, August 16 2024 15:09:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143205-143207 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#175856

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.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+

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.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.7%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-19  9:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240816150926.5789-5-pbhagavatula@marvell.com>
2024-08-16 14:44 ` |SUCCESS| pw143205-143207 [PATCH v4 5/5] node: add error stats for ip4 reassembly node qemudev
2024-08-16 14:48 ` qemudev
2024-08-16 15:10 ` |SUCCESS| pw143207 " checkpatch
2024-08-16 16:02 ` 0-day Robot
2024-08-19  8:20 ` |SUCCESS| pw143205-143207 [PATCH] [v4,5/5] node: add error stats for dpdklab
2024-08-19  8:20 ` dpdklab
2024-08-19  8:31 ` dpdklab
2024-08-19  8:33 ` dpdklab
2024-08-19  8:33 ` dpdklab
2024-08-19  8:36 ` dpdklab
2024-08-19  9:02 ` dpdklab
2024-08-19  9:03 ` dpdklab [this message]
2024-08-19  9:11 ` dpdklab
2024-08-19  9:16 ` dpdklab
2024-08-19  9:17 ` dpdklab
2024-08-19  9:29 ` dpdklab
2024-08-19  9:38 ` dpdklab
2024-08-19  9:41 ` dpdklab
2024-08-19 10:10 ` dpdklab
2024-08-19 10:16 ` dpdklab
2024-08-19 10:20 ` dpdklab
2024-08-19 10:42 ` dpdklab
2024-08-19 12:16 ` 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=66c30a55.050a0220.9ee41.4352SMTPIN_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).