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| pw142497 [PATCH] [v5] net/ark: fix index arithmetic bug
Date: Wed, 17 Jul 2024 18:32:26 -0700 (PDT)	[thread overview]
Message-ID: <669870aa.050a0220.15b3a9.18caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240717203830.2648483-1-ed.czeck@atomicrules.com>

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

_Performance Testing pending_

Submitter: Ed Czeck <ed.czeck@atomicrules.com>
Date: Wednesday, July 17 2024 20:38:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3317515e9377c13e458e31a64f8987a9d1f2eaf6

142497 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#168643

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

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

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-18  1:32 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240717203830.2648483-1-ed.czeck@atomicrules.com>
2024-07-17 20:16 ` |SUCCESS| pw142497 [PATCH v5] " qemudev
2024-07-17 20:20 ` qemudev
2024-07-17 20:38 ` checkpatch
2024-07-17 21:43 ` 0-day Robot
2024-07-18  0:52 ` |SUCCESS| pw142497 [PATCH] [v5] " dpdklab
2024-07-18  0:56 ` dpdklab
2024-07-18  1:00 ` dpdklab
2024-07-18  1:03 ` dpdklab
2024-07-18  1:09 ` dpdklab
2024-07-18  1:13 ` dpdklab
2024-07-18  1:16 ` dpdklab
2024-07-18  1:23 ` dpdklab
2024-07-18  1:32 ` dpdklab [this message]
2024-07-18  1:33 ` dpdklab
2024-07-18  1:39 ` dpdklab
2024-07-18  2:11 ` |PENDING| " dpdklab
2024-07-18  2:11 ` dpdklab
2024-07-18  2:11 ` dpdklab
2024-07-18  2:11 ` dpdklab
2024-07-18  2:14 ` |SUCCESS| " dpdklab
2024-07-18  2:15 ` |PENDING| " dpdklab
2024-07-18  2:19 ` dpdklab
2024-07-18  2:19 ` dpdklab
2024-07-18  2:20 ` dpdklab
2024-07-18  2:20 ` dpdklab
2024-07-18  2:21 ` dpdklab
2024-07-18  2:25 ` dpdklab
2024-07-18  2:27 ` dpdklab
2024-07-18  2:27 ` dpdklab
2024-07-18  2:31 ` dpdklab
2024-07-18  2:33 ` dpdklab
2024-07-18  2:36 ` dpdklab
2024-07-18  2:40 ` dpdklab
2024-07-18  2:41 ` dpdklab
2024-07-18  2:42 ` dpdklab
2024-07-18  2:42 ` dpdklab
2024-07-18  2:44 ` dpdklab
2024-07-18  2:45 ` dpdklab
2024-07-18  2:47 ` dpdklab
2024-07-18  2:48 ` dpdklab
2024-07-18  2:48 ` dpdklab
2024-07-18  3:25 ` dpdklab
2024-07-18  3:30 ` dpdklab
2024-07-18  3:30 ` dpdklab
2024-07-18  3:32 ` dpdklab
2024-07-18  3:36 ` dpdklab
2024-07-18  3:37 ` dpdklab
2024-07-18  3:37 ` dpdklab
2024-07-18  3:38 ` dpdklab
2024-07-18  3:39 ` dpdklab
2024-07-18  3:39 ` dpdklab
2024-07-18  3:39 ` dpdklab
2024-07-18  3:41 ` dpdklab
2024-07-18  3:43 ` dpdklab
2024-07-18  3:43 ` dpdklab
2024-07-18  3:44 ` dpdklab
2024-07-18  3:44 ` dpdklab
2024-07-18  3:46 ` dpdklab
2024-07-18  3:48 ` dpdklab
2024-07-18  3:51 ` dpdklab
2024-07-18  3:52 ` dpdklab
2024-07-18  3:54 ` dpdklab
2024-07-18  3:56 ` dpdklab
2024-07-18  3:59 ` dpdklab
2024-07-18  4:03 ` dpdklab
2024-07-18  4:06 ` dpdklab
2024-07-18  4:07 ` dpdklab
2024-07-18  4:07 ` |SUCCESS| " dpdklab
2024-07-18  4:08 ` |PENDING| " dpdklab
2024-07-18  4:09 ` dpdklab
2024-07-18  4:09 ` dpdklab
2024-07-18  4:10 ` |SUCCESS| " dpdklab
2024-07-18  4:11 ` |PENDING| " dpdklab
2024-07-18  4:12 ` |SUCCESS| " dpdklab
2024-07-18  4:13 ` |PENDING| " dpdklab
2024-07-18  4:13 ` dpdklab
2024-07-18  4:15 ` dpdklab
2024-07-18  4:16 ` |SUCCESS| " dpdklab
2024-07-18  4:18 ` |PENDING| " dpdklab
2024-07-18  4:20 ` dpdklab
2024-07-18  4:20 ` |SUCCESS| " dpdklab
2024-07-18  4:21 ` |PENDING| " dpdklab
2024-07-18  4:25 ` dpdklab
2024-07-18  4:25 ` dpdklab
2024-07-18  4:29 ` dpdklab
2024-07-18  4:29 ` dpdklab
2024-07-18  4:33 ` |SUCCESS| " dpdklab
2024-07-18  4:33 ` dpdklab
2024-07-18  4:40 ` dpdklab
2024-07-18  4:41 ` |PENDING| " dpdklab
2024-07-18  4:44 ` |SUCCESS| " dpdklab
2024-07-18  4:55 ` |PENDING| " dpdklab
2024-07-18  4:58 ` dpdklab
2024-07-18  5:01 ` dpdklab
2024-07-18  5:01 ` dpdklab
2024-07-18  5:01 ` dpdklab
2024-07-18  5:02 ` dpdklab
2024-07-18  5:04 ` dpdklab
2024-07-18  5:07 ` dpdklab
2024-07-18  5:14 ` dpdklab
2024-07-18  5:16 ` dpdklab
2024-07-18  5:16 ` dpdklab
2024-07-18  5:17 ` dpdklab
2024-07-18  5:18 ` |SUCCESS| " dpdklab
2024-07-18  5:18 ` dpdklab
2024-07-18  5:20 ` dpdklab
2024-07-18  5:21 ` |PENDING| " dpdklab
2024-07-18  5:23 ` dpdklab
2024-07-18  5:25 ` dpdklab
2024-07-18  5:27 ` dpdklab
2024-07-18  5:37 ` dpdklab
2024-07-18  5:55 ` dpdklab
2024-07-18  6:19 ` dpdklab
2024-07-18 15:00 ` |SUCCESS| " 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=669870aa.050a0220.15b3a9.18caSMTPIN_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).