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| pw139627 [PATCH] [v3] MAINTAINERS: remove maintainers that
Date: Tue, 23 Apr 2024 07:15:40 -0700 (PDT)	[thread overview]
Message-ID: <6627c28c.050a0220.f99d4.be9bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240422183958.6338-1-stephen@networkplumber.org>

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, April 22 2024 18:39:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139627 --> 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           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.4%                        |
+------------+---------+----------+-------------+------------------------------+

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

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

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-23 14:15 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240422183958.6338-1-stephen@networkplumber.org>
2024-04-22 18:14 ` |SUCCESS| pw139627 [PATCH v3] MAINTAINERS: remove maintainers that bounce qemudev
2024-04-22 18:19 ` qemudev
2024-04-22 18:41 ` checkpatch
2024-04-22 19:45 ` 0-day Robot
2024-04-23 11:18 ` |SUCCESS| pw139627 [PATCH] [v3] MAINTAINERS: remove maintainers that dpdklab
2024-04-23 11:36 ` dpdklab
2024-04-23 11:48 ` dpdklab
2024-04-23 11:50 ` dpdklab
2024-04-23 11:54 ` dpdklab
2024-04-23 11:55 ` dpdklab
2024-04-23 11:56 ` dpdklab
2024-04-23 11:56 ` dpdklab
2024-04-23 11:58 ` dpdklab
2024-04-23 11:58 ` dpdklab
2024-04-23 11:59 ` dpdklab
2024-04-23 12:00 ` dpdklab
2024-04-23 12:00 ` dpdklab
2024-04-23 12:00 ` dpdklab
2024-04-23 12:02 ` dpdklab
2024-04-23 12:02 ` dpdklab
2024-04-23 12:03 ` dpdklab
2024-04-23 12:03 ` dpdklab
2024-04-23 12:09 ` dpdklab
2024-04-23 12:13 ` dpdklab
2024-04-23 12:14 ` dpdklab
2024-04-23 12:14 ` dpdklab
2024-04-23 12:17 ` dpdklab
2024-04-23 12:19 ` dpdklab
2024-04-23 12:20 ` dpdklab
2024-04-23 12:21 ` dpdklab
2024-04-23 12:22 ` dpdklab
2024-04-23 12:25 ` dpdklab
2024-04-23 12:28 ` dpdklab
2024-04-23 12:28 ` dpdklab
2024-04-23 12:28 ` dpdklab
2024-04-23 12:35 ` dpdklab
2024-04-23 12:36 ` dpdklab
2024-04-23 12:59 ` dpdklab
2024-04-23 13:16 ` dpdklab
2024-04-23 13:19 ` dpdklab
2024-04-23 13:20 ` dpdklab
2024-04-23 13:22 ` dpdklab
2024-04-23 13:23 ` dpdklab
2024-04-23 13:26 ` dpdklab
2024-04-23 13:32 ` dpdklab
2024-04-23 13:34 ` dpdklab
2024-04-23 13:35 ` dpdklab
2024-04-23 13:35 ` dpdklab
2024-04-23 13:35 ` dpdklab
2024-04-23 13:36 ` dpdklab
2024-04-23 13:36 ` dpdklab
2024-04-23 13:37 ` dpdklab
2024-04-23 13:38 ` dpdklab
2024-04-23 13:39 ` dpdklab
2024-04-23 13:39 ` dpdklab
2024-04-23 13:41 ` dpdklab
2024-04-23 13:42 ` dpdklab
2024-04-23 13:42 ` dpdklab
2024-04-23 13:43 ` dpdklab
2024-04-23 13:43 ` dpdklab
2024-04-23 13:43 ` dpdklab
2024-04-23 13:44 ` dpdklab
2024-04-23 13:44 ` dpdklab
2024-04-23 13:44 ` dpdklab
2024-04-23 13:46 ` dpdklab
2024-04-23 13:49 ` dpdklab
2024-04-23 13:50 ` dpdklab
2024-04-23 13:51 ` dpdklab
2024-04-23 13:51 ` dpdklab
2024-04-23 13:52 ` dpdklab
2024-04-23 13:52 ` dpdklab
2024-04-23 13:54 ` dpdklab
2024-04-23 13:54 ` dpdklab
2024-04-23 13:55 ` dpdklab
2024-04-23 13:55 ` dpdklab
2024-04-23 13:57 ` dpdklab
2024-04-23 13:57 ` dpdklab
2024-04-23 13:58 ` dpdklab
2024-04-23 13:58 ` dpdklab
2024-04-23 13:58 ` dpdklab
2024-04-23 14:01 ` dpdklab
2024-04-23 14:02 ` dpdklab
2024-04-23 14:02 ` dpdklab
2024-04-23 14:09 ` dpdklab
2024-04-23 14:13 ` dpdklab
2024-04-23 14:15 ` dpdklab [this message]
2024-04-23 14:22 ` dpdklab
2024-04-23 14:23 ` dpdklab
2024-04-23 14:32 ` dpdklab
2024-04-23 14:44 ` dpdklab
2024-04-23 14:49 ` dpdklab
2024-04-23 16:02 ` dpdklab
2024-04-23 16:32 ` 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=6627c28c.050a0220.f99d4.be9bSMTPIN_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).