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| pw143397 [PATCH] [v2,1/1] dts: add methods for modifying M
Date: Tue, 27 Aug 2024 03:43:26 -0700 (PDT)	[thread overview]
Message-ID: <66cdadce.050a0220.d95c7.63b5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240826211327.16082-2-jspewock@iol.unh.edu>

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

_Performance Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Monday, August 26 2024 21:13:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143397 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#177239

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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 1.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

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.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+

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

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-27 10:43 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240826211327.16082-2-jspewock@iol.unh.edu>
2024-08-26 20:47 ` |SUCCESS| pw143397 [PATCH v2 1/1] dts: add methods for modifying MTU to testpmd shell qemudev
2024-08-26 20:52 ` qemudev
2024-08-26 21:15 ` checkpatch
2024-08-26 22:03 ` 0-day Robot
2024-08-27 10:24 ` |SUCCESS| pw143397 [PATCH] [v2,1/1] dts: add methods for modifying M dpdklab
2024-08-27 10:26 ` |PENDING| " dpdklab
2024-08-27 10:30 ` |SUCCESS| " dpdklab
2024-08-27 10:34 ` dpdklab
2024-08-27 10:36 ` |PENDING| " dpdklab
2024-08-27 10:43 ` dpdklab [this message]
2024-08-27 10:43 ` |FAILURE| " dpdklab
2024-08-27 10:44 ` |SUCCESS| " dpdklab
2024-08-27 10:46 ` dpdklab
2024-08-27 10:46 ` dpdklab
2024-08-27 11:35 ` |PENDING| " dpdklab
2024-08-27 12:06 ` dpdklab
2024-08-27 12:15 ` |SUCCESS| " dpdklab
2024-08-27 12:18 ` dpdklab
2024-08-27 12:19 ` dpdklab
2024-08-27 12:32 ` |FAILURE| " dpdklab
2024-08-27 12:45 ` |SUCCESS| " dpdklab
2024-08-27 12:46 ` |FAILURE| " dpdklab
2024-08-27 12:46 ` |SUCCESS| " dpdklab
2024-08-27 12:47 ` dpdklab
2024-08-27 12:48 ` |FAILURE| " dpdklab
2024-08-27 12:48 ` |SUCCESS| " dpdklab
2024-08-27 12:49 ` |FAILURE| " dpdklab
2024-08-27 12:49 ` |SUCCESS| " dpdklab
2024-08-27 12:49 ` dpdklab
2024-08-27 12:49 ` |FAILURE| " dpdklab
2024-08-27 12:50 ` |SUCCESS| " dpdklab
2024-08-27 12:50 ` |FAILURE| " dpdklab
2024-08-27 12:50 ` dpdklab
2024-08-27 12:51 ` dpdklab
2024-08-27 12:51 ` dpdklab
2024-08-27 12:51 ` dpdklab
2024-08-27 12:52 ` dpdklab
2024-08-27 12:52 ` dpdklab
2024-08-27 12:52 ` |SUCCESS| " dpdklab
2024-08-27 12:55 ` dpdklab
2024-08-27 12:56 ` dpdklab
2024-08-27 12:56 ` dpdklab
2024-08-27 12:56 ` dpdklab
2024-08-27 12:57 ` dpdklab
2024-08-27 12:57 ` dpdklab
2024-08-27 12:57 ` dpdklab
2024-08-27 12:58 ` dpdklab
2024-08-27 12:58 ` dpdklab
2024-08-27 12:58 ` dpdklab
2024-08-27 12:58 ` dpdklab
2024-08-27 12:59 ` dpdklab
2024-08-27 12:59 ` dpdklab
2024-08-27 13:00 ` dpdklab
2024-08-27 13:01 ` |FAILURE| " dpdklab
2024-08-27 13:01 ` |SUCCESS| " dpdklab
2024-08-27 13:01 ` dpdklab
2024-08-27 13:01 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:02 ` dpdklab
2024-08-27 13:03 ` dpdklab
2024-08-27 13:03 ` dpdklab
2024-08-27 13:06 ` dpdklab
2024-08-27 13:58 ` dpdklab
2024-08-27 14:00 ` dpdklab
2024-08-27 14:02 ` dpdklab
2024-08-27 14:07 ` dpdklab
2024-08-27 14:54 ` dpdklab
2024-08-27 15:31 ` dpdklab
2024-08-27 18:22 ` dpdklab
2024-08-27 18:42 ` dpdklab
2024-09-20  0:57 ` dpdklab
2024-09-20  1:16 ` dpdklab
2024-09-20  1:28 ` dpdklab
2024-09-20  1:47 ` 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=66cdadce.050a0220.d95c7.63b5SMTPIN_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).