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| pw142557 [PATCH] net/ice: fix DCF init for E830 devices
Date: Fri, 19 Jul 2024 10:01:35 -0700 (PDT)	[thread overview]
Message-ID: <669a9bef.050a0220.71887.610bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240719134427.10512-1-ian.stokes@intel.com>

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

_Performance Testing pending_

Submitter: Ian Stokes <ian.stokes@intel.com>
Date: Friday, July 19 2024 13:44:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142557 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#169165

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.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 3.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

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-19 17:01 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240719134427.10512-1-ian.stokes@intel.com>
2024-07-19 13:41 ` |SUCCESS| " qemudev
2024-07-19 13:44 ` checkpatch
2024-07-19 13:46 ` qemudev
2024-07-19 14:43 ` 0-day Robot
2024-07-19 16:35 ` dpdklab
2024-07-19 16:39 ` dpdklab
2024-07-19 16:43 ` dpdklab
2024-07-19 16:44 ` dpdklab
2024-07-19 16:52 ` dpdklab
2024-07-19 16:56 ` dpdklab
2024-07-19 16:57 ` dpdklab
2024-07-19 16:59 ` dpdklab
2024-07-19 17:01 ` dpdklab [this message]
2024-07-19 17:02 ` dpdklab
2024-07-19 17:08 ` dpdklab
2024-07-19 17:44 ` dpdklab
2024-07-19 17:51 ` |PENDING| " dpdklab
2024-07-19 18:03 ` dpdklab
2024-07-19 18:20 ` dpdklab
2024-07-19 18:25 ` dpdklab
2024-07-19 18:35 ` dpdklab
2024-07-19 18:35 ` dpdklab
2024-07-19 18:39 ` dpdklab
2024-07-19 18:44 ` dpdklab
2024-07-19 18:52 ` dpdklab
2024-07-19 18:54 ` dpdklab
2024-07-19 18:57 ` dpdklab
2024-07-19 18:57 ` dpdklab
2024-07-19 19:00 ` dpdklab
2024-07-19 19:02 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:04 ` dpdklab
2024-07-19 19:05 ` dpdklab
2024-07-19 19:08 ` dpdklab
2024-07-19 19:11 ` dpdklab
2024-07-19 19:12 ` dpdklab
2024-07-19 19:15 ` dpdklab
2024-07-19 19:19 ` dpdklab
2024-07-19 19:22 ` dpdklab
2024-07-19 19:25 ` dpdklab
2024-07-19 19:26 ` dpdklab
2024-07-19 19:27 ` dpdklab
2024-07-19 19:28 ` dpdklab
2024-07-19 19:33 ` dpdklab
2024-07-19 19:34 ` dpdklab
2024-07-19 19:35 ` |SUCCESS| " dpdklab
2024-07-19 19:35 ` dpdklab
2024-07-19 19:36 ` |PENDING| " dpdklab
2024-07-19 19:36 ` dpdklab
2024-07-19 19:37 ` dpdklab
2024-07-19 19:39 ` dpdklab
2024-07-19 19:57 ` |SUCCESS| " dpdklab
2024-07-19 19:57 ` |PENDING| " dpdklab
2024-07-19 20:00 ` |SUCCESS| " dpdklab
2024-07-19 20:01 ` dpdklab
2024-07-19 20:02 ` |PENDING| " dpdklab
2024-07-19 20:02 ` dpdklab
2024-07-19 20:02 ` dpdklab
2024-07-19 20:05 ` dpdklab
2024-07-19 20:06 ` |SUCCESS| " dpdklab
2024-07-19 20:06 ` |PENDING| " dpdklab
2024-07-19 20:10 ` dpdklab
2024-07-19 20:10 ` dpdklab
2024-07-19 20:12 ` dpdklab
2024-07-19 20:14 ` dpdklab
2024-07-19 20:15 ` dpdklab
2024-07-19 20:15 ` dpdklab
2024-07-19 20:17 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:19 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:23 ` dpdklab
2024-07-19 20:24 ` dpdklab
2024-07-19 20:24 ` dpdklab
2024-07-19 20:25 ` dpdklab
2024-07-19 20:25 ` |SUCCESS| " dpdklab
2024-07-19 20:27 ` |PENDING| " dpdklab
2024-07-19 20:27 ` dpdklab
2024-07-19 20:28 ` dpdklab
2024-07-19 20:30 ` |SUCCESS| " dpdklab
2024-07-19 20:30 ` |PENDING| " dpdklab
2024-07-19 20:30 ` dpdklab
2024-07-19 20:32 ` dpdklab
2024-07-19 20:33 ` dpdklab
2024-07-19 20:34 ` dpdklab
2024-07-19 20:37 ` dpdklab
2024-07-19 20:38 ` |SUCCESS| " dpdklab
2024-07-19 20:40 ` |PENDING| " dpdklab
2024-07-19 20:42 ` dpdklab
2024-07-19 20:45 ` dpdklab
2024-07-19 20:45 ` dpdklab
2024-07-19 20:57 ` dpdklab
2024-07-19 21:11 ` dpdklab
2024-07-19 21:20 ` dpdklab
2024-07-19 21:26 ` dpdklab
2024-07-19 21:37 ` dpdklab
2024-07-19 21:38 ` |SUCCESS| " dpdklab
2024-07-20  1: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=669a9bef.050a0220.71887.610bSMTPIN_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).