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| pw143594 [PATCH] [v1,1/1] dts: add send_packets to test su
Date: Wed, 04 Sep 2024 17:51:13 -0700 (PDT)	[thread overview]
Message-ID: <66d90081.050a0220.29b5c7.a585SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240904152827.11914-2-jspewock@iol.unh.edu>

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

_Performance Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, September 04 2024 15:28:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143594 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#178331

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-05  0:51 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240904152827.11914-2-jspewock@iol.unh.edu>
2024-09-04 15:11 ` |SUCCESS| pw143594 [PATCH v1 1/1] dts: add send_packets to test suites and rework packet addressing qemudev
2024-09-04 15:15 ` qemudev
2024-09-04 15:29 ` checkpatch
2024-09-04 16:24 ` 0-day Robot
2024-09-04 20:14 ` |SUCCESS| pw143594 [PATCH] [v1,1/1] dts: add send_packets to test su dpdklab
2024-09-04 20:14 ` dpdklab
2024-09-04 20:26 ` |PENDING| " dpdklab
2024-09-04 20:27 ` |SUCCESS| " dpdklab
2024-09-04 20:28 ` |PENDING| " dpdklab
2024-09-04 20:34 ` |SUCCESS| " dpdklab
2024-09-04 21:02 ` dpdklab
2024-09-04 22:42 ` |PENDING| " dpdklab
2024-09-04 23:00 ` |SUCCESS| " dpdklab
2024-09-04 23:46 ` |PENDING| " dpdklab
2024-09-04 23:50 ` |SUCCESS| " dpdklab
2024-09-05  0:21 ` dpdklab
2024-09-05  0:22 ` dpdklab
2024-09-05  0:26 ` dpdklab
2024-09-05  0:26 ` dpdklab
2024-09-05  0:26 ` dpdklab
2024-09-05  0:27 ` dpdklab
2024-09-05  0:28 ` dpdklab
2024-09-05  0:28 ` dpdklab
2024-09-05  0:29 ` dpdklab
2024-09-05  0:30 ` dpdklab
2024-09-05  0:31 ` dpdklab
2024-09-05  0:31 ` dpdklab
2024-09-05  0:32 ` dpdklab
2024-09-05  0:32 ` dpdklab
2024-09-05  0:32 ` dpdklab
2024-09-05  0:33 ` dpdklab
2024-09-05  0:34 ` dpdklab
2024-09-05  0:35 ` dpdklab
2024-09-05  0:37 ` dpdklab
2024-09-05  0:38 ` |PENDING| " dpdklab
2024-09-05  0:43 ` |SUCCESS| " dpdklab
2024-09-05  0:43 ` dpdklab
2024-09-05  0:43 ` dpdklab
2024-09-05  0:44 ` dpdklab
2024-09-05  0:45 ` dpdklab
2024-09-05  0:48 ` dpdklab
2024-09-05  0:49 ` dpdklab
2024-09-05  0:51 ` dpdklab [this message]
2024-09-05  0:51 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:52 ` dpdklab
2024-09-05  0:53 ` dpdklab
2024-09-05  0:53 ` dpdklab
2024-09-05  0:53 ` dpdklab
2024-09-05  0:55 ` dpdklab
2024-09-05  0:55 ` dpdklab
2024-09-05  0:55 ` dpdklab
2024-09-05  0:56 ` dpdklab
2024-09-05  0:56 ` dpdklab
2024-09-05  0:56 ` dpdklab
2024-09-05  0:57 ` dpdklab
2024-09-05  0:57 ` dpdklab
2024-09-05  0:58 ` dpdklab
2024-09-05  1:07 ` dpdklab
2024-09-05  1:08 ` dpdklab
2024-09-05  1:08 ` dpdklab
2024-09-05  1:08 ` dpdklab
2024-09-05  1:09 ` dpdklab
2024-09-05  1:10 ` dpdklab
2024-09-05  1:11 ` dpdklab
2024-09-05  1:11 ` dpdklab
2024-09-05  1:31 ` dpdklab
2024-09-05  1:43 ` dpdklab
2024-09-05  2:08 ` dpdklab
2024-09-05  2:43 ` dpdklab
2024-09-05  2:58 ` dpdklab
2024-09-05  3:06 ` dpdklab
2024-09-05  3:35 ` dpdklab
2024-09-05  3:36 ` dpdklab
2024-09-05  3:44 ` dpdklab
2024-09-05  4:19 ` dpdklab
2024-09-05  8:49 ` dpdklab
2024-09-12 15:18 ` dpdklab
2024-09-18  7:22 ` dpdklab
2024-09-18  7:42 ` dpdklab
2024-09-18  8:01 ` dpdklab
2024-09-18  8: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=66d90081.050a0220.29b5c7.a585SMTPIN_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).