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| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op
Date: Wed, 17 Apr 2024 04:43:26 -0700 (PDT)	[thread overview]
Message-ID: <661fb5de.050a0220.cb391.5cf0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417072708.322-8-anoobj@marvell.com>

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

_Performance Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, April 17 2024 07:27:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139438-139444 --> 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.8%                         |
+------------+---------+----------+-------------+------------------------------+
| 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
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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -2.5%                        |
+------------+---------+----------+-------------+------------------------------+

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

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-17 11:43 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417072708.322-8-anoobj@marvell.com>
2024-04-17  7:11 ` |SUCCESS| pw139438-139444 [PATCH v2 7/7] dma/odm: add remaining ops qemudev
2024-04-17  7:15 ` qemudev
2024-04-17  7:29 ` |WARNING| pw139444 " checkpatch
2024-04-17  8:44 ` |FAILURE| " 0-day Robot
2024-04-17  9:51 ` |SUCCESS| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op dpdklab
2024-04-17  9:52 ` dpdklab
2024-04-17  9:53 ` dpdklab
2024-04-17  9:54 ` dpdklab
2024-04-17  9:55 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:21 ` dpdklab
2024-04-17 10:23 ` dpdklab
2024-04-17 10:25 ` dpdklab
2024-04-17 10:26 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:28 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:43 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:51 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:20 ` dpdklab
2024-04-17 11:24 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:43 ` dpdklab [this message]
2024-04-17 11:47 ` dpdklab
2024-04-17 11:49 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 12:00 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` 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=661fb5de.050a0220.cb391.5cf0SMTPIN_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).