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: |PENDING| pw142234-142237 [PATCH] [v3,4/4] dts: dynamic config test
Date: Mon, 08 Jul 2024 16:01:51 -0700 (PDT)	[thread overview]
Message-ID: <668c6fdf.050a0220.cfa61.124fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240708193012.5465-4-dmarx@iol.unh.edu>

Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/142237

_Performance Testing pending_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Monday, July 08 2024 19:30:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e6bfd9676109f904b4f263402e77105fdca8e67c

142234-142237 --> performance testing pending

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.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 2.5%                         |
+------------+---------+----------+-------------+------------------------------+

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/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-08 23:01 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240708193012.5465-4-dmarx@iol.unh.edu>
2024-07-08 19:05 ` |SUCCESS| pw142234-142237 [PATCH v3 4/4] dts: dynamic config test suite qemudev
2024-07-08 19:09 ` qemudev
2024-07-08 19:32 ` |SUCCESS| pw142237 " checkpatch
2024-07-08 20:43 ` 0-day Robot
2024-07-08 22:58 ` |PENDING| pw142234-142237 [PATCH] [v3,4/4] dts: dynamic config test dpdklab
2024-07-08 23:01 ` dpdklab [this message]
2024-07-08 23:02 ` dpdklab
2024-07-08 23:02 ` dpdklab
2024-07-08 23:04 ` dpdklab
2024-07-08 23:05 ` |SUCCESS| " dpdklab
2024-07-08 23:09 ` dpdklab
2024-07-08 23:15 ` dpdklab
2024-07-08 23:15 ` dpdklab
2024-07-08 23:19 ` dpdklab
2024-07-08 23:22 ` dpdklab
2024-07-08 23:22 ` |PENDING| " dpdklab
2024-07-08 23:22 ` dpdklab
2024-07-08 23:25 ` dpdklab
2024-07-08 23:29 ` dpdklab
2024-07-08 23:30 ` dpdklab
2024-07-08 23:30 ` dpdklab
2024-07-08 23:34 ` dpdklab
2024-07-08 23:36 ` dpdklab
2024-07-08 23:37 ` dpdklab
2024-07-08 23:38 ` dpdklab
2024-07-08 23:38 ` dpdklab
2024-07-08 23:40 ` dpdklab
2024-07-08 23:41 ` dpdklab
2024-07-08 23:41 ` dpdklab
2024-07-08 23:43 ` |SUCCESS| " dpdklab
2024-07-08 23:44 ` dpdklab
2024-07-08 23:48 ` |PENDING| " dpdklab
2024-07-08 23:49 ` dpdklab
2024-07-08 23:53 ` dpdklab
2024-07-08 23:54 ` dpdklab
2024-07-08 23:54 ` dpdklab
2024-07-08 23:54 ` dpdklab
2024-07-08 23:57 ` |SUCCESS| " dpdklab
2024-07-08 23:59 ` |PENDING| " dpdklab
2024-07-09  0:22 ` dpdklab
2024-07-09  1:07 ` dpdklab
2024-07-09  1:15 ` dpdklab
2024-07-09  1:15 ` dpdklab
2024-07-09  1:18 ` dpdklab
2024-07-09  1:18 ` dpdklab
2024-07-09  1:27 ` dpdklab
2024-07-09  1:32 ` dpdklab
2024-07-09  1:32 ` dpdklab
2024-07-09  1:34 ` dpdklab
2024-07-09  1:37 ` dpdklab
2024-07-09  1:40 ` dpdklab
2024-07-09  1:42 ` dpdklab
2024-07-09  1:43 ` dpdklab
2024-07-09  1:47 ` dpdklab
2024-07-09  1:51 ` dpdklab
2024-07-09  1:53 ` dpdklab
2024-07-09  1:57 ` |SUCCESS| " dpdklab
2024-07-09  2:44 ` |PENDING| " dpdklab
2024-07-09  2:52 ` dpdklab
2024-07-09  2:59 ` dpdklab
2024-07-09  3:04 ` dpdklab
2024-07-09  3:07 ` dpdklab
2024-07-09  3:10 ` dpdklab
2024-07-09  3:15 ` dpdklab
2024-07-09  3:16 ` dpdklab
2024-07-09  3:18 ` dpdklab
2024-07-09  3:18 ` dpdklab
2024-07-09  3:20 ` dpdklab
2024-07-09  3:22 ` dpdklab
2024-07-09  3:27 ` dpdklab
2024-07-09  3:28 ` dpdklab
2024-07-09  3:29 ` dpdklab
2024-07-09  3:29 ` dpdklab
2024-07-09  3:30 ` dpdklab
2024-07-09  3:33 ` dpdklab
2024-07-09  3:34 ` dpdklab
2024-07-09  3:37 ` dpdklab
2024-07-09  3:37 ` dpdklab
2024-07-09  3:37 ` dpdklab
2024-07-09  3:39 ` dpdklab
2024-07-09  3:49 ` dpdklab
2024-07-09  3:51 ` dpdklab
2024-07-09  3:52 ` dpdklab
2024-07-09  3:54 ` dpdklab
2024-07-09  4:04 ` dpdklab
2024-07-09  4:11 ` dpdklab
2024-07-09  4:13 ` dpdklab
2024-07-09  4:17 ` dpdklab
2024-07-09  4:20 ` dpdklab
2024-07-09  4:24 ` dpdklab
2024-07-09  4:27 ` dpdklab
2024-07-09  4:28 ` dpdklab
2024-07-09  4:32 ` dpdklab
2024-07-09  4:33 ` dpdklab
2024-07-09  4:36 ` dpdklab
2024-07-09  4:40 ` dpdklab
2024-07-09  4:40 ` dpdklab
2024-07-09  4:44 ` dpdklab
2024-07-09  4:47 ` dpdklab
2024-07-09  4:48 ` |SUCCESS| " dpdklab
2024-07-09  4:50 ` |PENDING| " dpdklab
2024-07-09  4:53 ` dpdklab
2024-07-09  4:58 ` dpdklab
2024-07-09  5:35 ` dpdklab
2024-07-09  5:47 ` dpdklab
2024-07-09  5:51 ` |SUCCESS| " dpdklab
2024-07-09  5:51 ` |PENDING| " dpdklab
2024-07-09  5:55 ` |SUCCESS| " dpdklab
2024-07-09 19:36 ` dpdklab
2024-07-09 21:03 ` dpdklab
2024-07-09 21:15 ` dpdklab
2024-07-13 18:43 ` dpdklab
2024-07-14  9:48 ` dpdklab
2024-07-15  6:54 ` dpdklab
2024-07-15  7:29 ` dpdklab
2024-07-15 13:18 ` 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=668c6fdf.050a0220.cfa61.124fSMTPIN_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).