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| pw142841-142847 [PATCH] [v11,7/7] drivers: remove use of t
Date: Thu, 01 Aug 2024 12:30:12 -0700 (PDT)	[thread overview]
Message-ID: <66abe244.050a0220.13ef1d.10b8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801154821.150443-8-stephen@networkplumber.org>

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, August 01 2024 15:46:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142841-142847 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#172458

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

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

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.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

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

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801154821.150443-8-stephen@networkplumber.org>
2024-08-01 15:25 ` |SUCCESS| pw142841-142847 [PATCH v11 7/7] drivers: remove use of term sanity check qemudev
2024-08-01 15:30 ` qemudev
2024-08-01 15:51 ` |SUCCESS| pw142847 " checkpatch
2024-08-01 17:42 ` 0-day Robot
2024-08-01 19:12 ` |SUCCESS| pw142841-142847 [PATCH] [v11,7/7] drivers: remove use of t dpdklab
2024-08-01 19:13 ` |PENDING| " dpdklab
2024-08-01 19:26 ` |SUCCESS| " dpdklab
2024-08-01 19:30 ` dpdklab [this message]
2024-08-01 19:31 ` |PENDING| " dpdklab
2024-08-01 19:34 ` |SUCCESS| " dpdklab
2024-08-01 19:44 ` dpdklab
2024-08-01 19:46 ` |PENDING| " dpdklab
2024-08-01 19:49 ` dpdklab
2024-08-01 19:51 ` |SUCCESS| " dpdklab
2024-08-01 19:53 ` |PENDING| " dpdklab
2024-08-01 19:54 ` |SUCCESS| " dpdklab
2024-08-01 19:55 ` |PENDING| " dpdklab
2024-08-01 19:55 ` dpdklab
2024-08-01 19:55 ` dpdklab
2024-08-01 19:57 ` dpdklab
2024-08-01 19:59 ` dpdklab
2024-08-01 19:59 ` dpdklab
2024-08-01 20:00 ` dpdklab
2024-08-01 20:07 ` dpdklab
2024-08-01 20:08 ` dpdklab
2024-08-01 20:15 ` dpdklab
2024-08-01 20:18 ` |SUCCESS| " dpdklab
2024-08-01 20:19 ` dpdklab
2024-08-01 20:23 ` dpdklab
2024-08-01 20:26 ` dpdklab
2024-08-01 20:28 ` dpdklab
2024-08-01 20:44 ` |PENDING| " dpdklab
2024-08-01 20:46 ` dpdklab
2024-08-01 21:01 ` |SUCCESS| " dpdklab
2024-08-01 21:11 ` |PENDING| " dpdklab
2024-08-01 21:12 ` dpdklab
2024-08-01 21:14 ` dpdklab
2024-08-01 21:14 ` dpdklab
2024-08-01 21:15 ` dpdklab
2024-08-01 21:16 ` dpdklab
2024-08-01 21:21 ` dpdklab
2024-08-01 21:22 ` dpdklab
2024-08-01 21:38 ` dpdklab
2024-08-01 21:48 ` dpdklab
2024-08-01 22:00 ` dpdklab
2024-08-01 22:02 ` dpdklab
2024-08-01 22:09 ` dpdklab
2024-08-01 22:22 ` dpdklab
2024-08-01 22:31 ` dpdklab
2024-08-01 22:33 ` dpdklab
2024-08-01 22:35 ` dpdklab
2024-08-01 22:35 ` dpdklab
2024-08-01 22:36 ` dpdklab
2024-08-01 22:39 ` dpdklab
2024-08-01 22:40 ` dpdklab
2024-08-01 22:42 ` dpdklab
2024-08-01 22:42 ` dpdklab
2024-08-01 22:49 ` dpdklab
2024-08-01 22:50 ` dpdklab
2024-08-01 22:50 ` dpdklab
2024-08-01 22:50 ` dpdklab
2024-08-01 22:54 ` dpdklab
2024-08-01 22:57 ` dpdklab
2024-08-01 22:59 ` dpdklab
2024-08-01 23:00 ` dpdklab
2024-08-01 23:03 ` dpdklab
2024-08-01 23:03 ` dpdklab
2024-08-01 23:04 ` dpdklab
2024-08-01 23:04 ` dpdklab
2024-08-01 23:05 ` dpdklab
2024-08-01 23:06 ` dpdklab
2024-08-01 23:06 ` dpdklab
2024-08-01 23:07 ` dpdklab
2024-08-01 23:07 ` dpdklab
2024-08-01 23:08 ` dpdklab
2024-08-01 23:08 ` dpdklab
2024-08-01 23:11 ` dpdklab
2024-08-01 23:12 ` dpdklab
2024-08-01 23:13 ` dpdklab
2024-08-01 23:15 ` dpdklab
2024-08-01 23:16 ` dpdklab
2024-08-01 23:17 ` dpdklab
2024-08-01 23:17 ` dpdklab
2024-08-01 23:17 ` dpdklab
2024-08-01 23:17 ` dpdklab
2024-08-01 23:19 ` dpdklab
2024-08-01 23:20 ` dpdklab
2024-08-01 23:20 ` dpdklab
2024-08-01 23:22 ` dpdklab
2024-08-01 23:26 ` dpdklab
2024-08-01 23:26 ` dpdklab
2024-08-01 23:29 ` dpdklab
2024-08-01 23:33 ` dpdklab
2024-08-01 23:36 ` dpdklab
2024-08-01 23:36 ` dpdklab
2024-08-01 23:38 ` dpdklab
2024-08-01 23:39 ` dpdklab
2024-08-01 23:39 ` |SUCCESS| " dpdklab
2024-08-01 23:40 ` |PENDING| " dpdklab
2024-08-01 23:45 ` dpdklab
2024-08-01 23:51 ` dpdklab
2024-08-01 23:52 ` dpdklab
2024-08-02  0:17 ` dpdklab
2024-08-02  0:49 ` dpdklab
2024-08-02  0:52 ` dpdklab
2024-08-02  0:53 ` |SUCCESS| " dpdklab
2024-08-02  0:57 ` dpdklab
2024-08-02  0:59 ` |PENDING| " dpdklab
2024-08-02  1:14 ` |SUCCESS| " dpdklab
2024-08-02  1:15 ` dpdklab
2024-08-03  1:08 ` dpdklab
2024-08-06  3:07 ` dpdklab
2024-08-06  3:15 ` dpdklab
2024-08-06  3:29 ` 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=66abe244.050a0220.13ef1d.10b8SMTPIN_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).