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| pw140909 [PATCH] maintainers: update email address for PPC
Date: Wed, 12 Jun 2024 15:47:59 -0700 (PDT)	[thread overview]
Message-ID: <666a259f.170a0220.88555.0e6aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529173420.42401-1-drc@linux.vnet.ibm.com>

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

_Performance Testing PASS_

Submitter: David Christensen <drc@linux.vnet.ibm.com>
Date: Wednesday, May 29 2024 17:34:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140909 --> performance testing pass

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
Target: Unknown
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | -1.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
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.3%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-12 22:48 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240529173420.42401-1-drc@linux.vnet.ibm.com>
2024-06-10 15:13 ` qemudev
2024-06-10 15:17 ` qemudev
2024-06-10 15:37 ` |WARNING| " checkpatch
2024-06-10 22:37 ` |SUCCESS| " dpdklab
2024-06-10 22:37 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:45 ` dpdklab
2024-06-10 22:46 ` dpdklab
2024-06-12 22:47 ` dpdklab
2024-06-12 22:47 ` dpdklab [this message]
2024-06-12 22:48 ` dpdklab
2024-06-12 22:48 ` dpdklab
2024-06-12 22:49 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:35 ` 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=666a259f.170a0220.88555.0e6aSMTPIN_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).