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| pw139544-139545 [PATCH] [v2,2/2] test/dma: add functions t
Date: Fri, 19 Apr 2024 09:40:00 -0700 (PDT)	[thread overview]
Message-ID: <66229e60.050a0220.4d03.a3e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240419090734.43613-2-vvelumuri@marvell.com>

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

_Performance Testing PASS_

Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Friday, April 19 2024 09:07:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139544-139545 --> 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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 3.0%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-19 16:40 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240419090734.43613-2-vvelumuri@marvell.com>
2024-04-19  8:55 ` |SUCCESS| pw139544-139545 [PATCH v2 2/2] test/dma: add functions to verify zero and one fill qemudev
2024-04-19  8:59 ` qemudev
2024-04-19  9:09 ` |SUCCESS| pw139545 " checkpatch
2024-04-19 10:25 ` 0-day Robot
2024-04-19 15:22 ` |SUCCESS| pw139544-139545 [PATCH] [v2,2/2] test/dma: add functions t dpdklab
2024-04-19 15:26 ` dpdklab
2024-04-19 15:26 ` dpdklab
2024-04-19 15:26 ` dpdklab
2024-04-19 15:27 ` dpdklab
2024-04-19 15:27 ` dpdklab
2024-04-19 15:29 ` dpdklab
2024-04-19 15:31 ` dpdklab
2024-04-19 15:31 ` dpdklab
2024-04-19 15:32 ` dpdklab
2024-04-19 15:32 ` dpdklab
2024-04-19 15:32 ` dpdklab
2024-04-19 16:04 ` dpdklab
2024-04-19 16:04 ` dpdklab
2024-04-19 16:05 ` dpdklab
2024-04-19 16:06 ` dpdklab
2024-04-19 16:07 ` dpdklab
2024-04-19 16:07 ` dpdklab
2024-04-19 16:07 ` dpdklab
2024-04-19 16:08 ` dpdklab
2024-04-19 16:08 ` dpdklab
2024-04-19 16:08 ` dpdklab
2024-04-19 16:08 ` dpdklab
2024-04-19 16:09 ` dpdklab
2024-04-19 16:09 ` dpdklab
2024-04-19 16:09 ` dpdklab
2024-04-19 16:09 ` dpdklab
2024-04-19 16:09 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:10 ` dpdklab
2024-04-19 16:11 ` dpdklab
2024-04-19 16:11 ` dpdklab
2024-04-19 16:11 ` dpdklab
2024-04-19 16:11 ` dpdklab
2024-04-19 16:11 ` dpdklab
2024-04-19 16:12 ` dpdklab
2024-04-19 16:12 ` dpdklab
2024-04-19 16:13 ` dpdklab
2024-04-19 16:14 ` dpdklab
2024-04-19 16:14 ` dpdklab
2024-04-19 16:15 ` dpdklab
2024-04-19 16:16 ` dpdklab
2024-04-19 16:18 ` dpdklab
2024-04-19 16:20 ` dpdklab
2024-04-19 16:31 ` dpdklab
2024-04-19 16:36 ` dpdklab
2024-04-19 16:36 ` dpdklab
2024-04-19 16:36 ` dpdklab
2024-04-19 16:37 ` dpdklab
2024-04-19 16:37 ` dpdklab
2024-04-19 16:37 ` dpdklab
2024-04-19 16:37 ` dpdklab
2024-04-19 16:38 ` dpdklab
2024-04-19 16:38 ` dpdklab
2024-04-19 16:38 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:39 ` dpdklab
2024-04-19 16:40 ` dpdklab [this message]
2024-04-19 16:40 ` dpdklab
2024-04-19 16:40 ` dpdklab
2024-04-19 16:42 ` dpdklab
2024-04-19 16:42 ` dpdklab
2024-04-19 16:42 ` dpdklab
2024-04-19 16:42 ` dpdklab
2024-04-19 16:43 ` dpdklab
2024-04-19 16:43 ` dpdklab
2024-04-19 16:44 ` dpdklab
2024-04-19 16:44 ` dpdklab
2024-04-19 16:44 ` dpdklab
2024-04-19 16:45 ` dpdklab
2024-04-19 16:50 ` dpdklab
2024-04-19 16:56 ` dpdklab
2024-04-19 16:57 ` dpdklab
2024-04-19 16:59 ` dpdklab
2024-04-19 17:11 ` dpdklab
2024-04-19 17:13 ` 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=66229e60.050a0220.4d03.a3e4SMTPIN_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).