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| pw142854-142857 [PATCH] [v5,4/4] test-pmd: add more packet
Date: Thu, 01 Aug 2024 17:54:52 -0700 (PDT)	[thread overview]
Message-ID: <66ac2e5c.050a0220.25c917.1961SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801190617.201574-5-stephen@networkplumber.org>

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

_Performance Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, August 01 2024 19:04:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:37ce4c84c0f23c3989bc7ae19e03a4593cec94e5

142854-142857 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#172546

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

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

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-02  0:54 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801190617.201574-5-stephen@networkplumber.org>
2024-08-01 18:40 ` |SUCCESS| pw142854-142857 [PATCH v5 4/4] test-pmd: add more packet verbose decode options qemudev
2024-08-01 18:44 ` qemudev
2024-08-01 19:07 ` |WARNING| pw142857 " checkpatch
2024-08-01 20:02 ` |SUCCESS| " 0-day Robot
2024-08-01 22:19 ` |SUCCESS| pw142854-142857 [PATCH] [v5,4/4] test-pmd: add more packet dpdklab
2024-08-01 22:22 ` |PENDING| " dpdklab
2024-08-01 22:26 ` |SUCCESS| " dpdklab
2024-08-01 22:35 ` dpdklab
2024-08-01 22:38 ` dpdklab
2024-08-01 22:54 ` dpdklab
2024-08-01 23:59 ` |PENDING| " dpdklab
2024-08-01 23:59 ` dpdklab
2024-08-01 23:59 ` dpdklab
2024-08-02  0:04 ` |SUCCESS| " dpdklab
2024-08-02  0:04 ` dpdklab
2024-08-02  0:05 ` dpdklab
2024-08-02  0:09 ` |PENDING| " dpdklab
2024-08-02  0:09 ` dpdklab
2024-08-02  0:15 ` dpdklab
2024-08-02  0:16 ` dpdklab
2024-08-02  0:19 ` dpdklab
2024-08-02  0:27 ` dpdklab
2024-08-02  0:28 ` dpdklab
2024-08-02  0:29 ` dpdklab
2024-08-02  0:30 ` dpdklab
2024-08-02  0:34 ` dpdklab
2024-08-02  0:35 ` dpdklab
2024-08-02  0:40 ` dpdklab
2024-08-02  0:41 ` dpdklab
2024-08-02  0:42 ` dpdklab
2024-08-02  0:47 ` dpdklab
2024-08-02  0:54 ` dpdklab [this message]
2024-08-02  0:55 ` dpdklab
2024-08-02  0:58 ` dpdklab
2024-08-02  1:03 ` |SUCCESS| " dpdklab
2024-08-02  1:03 ` dpdklab
2024-08-02  1:38 ` dpdklab
2024-08-02  1:58 ` dpdklab
2024-08-02  1:59 ` |PENDING| " dpdklab
2024-08-02  2:02 ` |SUCCESS| " dpdklab
2024-08-02  2:07 ` dpdklab
2024-08-02  2:12 ` dpdklab
2024-08-02  2:32 ` dpdklab
2024-08-02  2:33 ` |PENDING| " dpdklab
2024-08-02  2:33 ` dpdklab
2024-08-02  2:39 ` dpdklab
2024-08-02  2:44 ` dpdklab
2024-08-02  2:51 ` dpdklab
2024-08-02  2:54 ` dpdklab
2024-08-02  2:55 ` dpdklab
2024-08-02  2:58 ` dpdklab
2024-08-02  3:04 ` dpdklab
2024-08-02  3:06 ` dpdklab
2024-08-02  3:07 ` dpdklab
2024-08-02  3:07 ` dpdklab
2024-08-02  3:07 ` dpdklab
2024-08-02  3:08 ` dpdklab
2024-08-02  3:09 ` dpdklab
2024-08-02  3:09 ` dpdklab
2024-08-02  3:10 ` dpdklab
2024-08-02  3:11 ` dpdklab
2024-08-02  3:17 ` dpdklab
2024-08-02  3:18 ` dpdklab
2024-08-02  3:18 ` dpdklab
2024-08-02  3:19 ` dpdklab
2024-08-02  3:24 ` dpdklab
2024-08-02  3:25 ` dpdklab
2024-08-02  3:26 ` dpdklab
2024-08-02  3:26 ` dpdklab
2024-08-02  3:29 ` dpdklab
2024-08-02  3:29 ` dpdklab
2024-08-02  3:36 ` dpdklab
2024-08-02  3:36 ` dpdklab
2024-08-02  3:37 ` dpdklab
2024-08-02  3:41 ` dpdklab
2024-08-02  3:42 ` dpdklab
2024-08-02  3:43 ` dpdklab
2024-08-02  3:44 ` dpdklab
2024-08-02  3:45 ` dpdklab
2024-08-02  3:45 ` dpdklab
2024-08-02  3:46 ` |SUCCESS| " dpdklab
2024-08-02  3:46 ` |PENDING| " dpdklab
2024-08-02  3:55 ` dpdklab
2024-08-02  3:56 ` dpdklab
2024-08-02  3:57 ` dpdklab
2024-08-02  3:57 ` dpdklab
2024-08-02  4:00 ` dpdklab
2024-08-02  4:01 ` dpdklab
2024-08-02  4:02 ` dpdklab
2024-08-02  4:02 ` dpdklab
2024-08-02  4:03 ` dpdklab
2024-08-02  4:05 ` dpdklab
2024-08-02  4:06 ` dpdklab
2024-08-02  4:06 ` dpdklab
2024-08-02  4:07 ` dpdklab
2024-08-02  4:08 ` dpdklab
2024-08-02  4:10 ` dpdklab
2024-08-02  4:10 ` dpdklab
2024-08-02  4:13 ` dpdklab
2024-08-02  4:13 ` |SUCCESS| " dpdklab
2024-08-02  4:13 ` |PENDING| " dpdklab
2024-08-02  4:16 ` dpdklab
2024-08-02  4:17 ` dpdklab
2024-08-02  4:23 ` dpdklab
2024-08-02  4:24 ` dpdklab
2024-08-02  4:36 ` |SUCCESS| " dpdklab
2024-08-02  4:42 ` dpdklab
2024-08-03  3:28 ` dpdklab
2024-08-06  5:47 ` dpdklab
2024-08-06  6:00 ` dpdklab
2024-08-06  6:12 ` 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=66ac2e5c.050a0220.25c917.1961SMTPIN_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).