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| pw142092 [PATCH] eal: make dev_sigbus static
Date: Thu, 04 Jul 2024 00:11:53 -0700 (PDT)	[thread overview]
Message-ID: <66864b39.050a0220.edda6.8cbaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703151734.14458-1-stephen@networkplumber.org>

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, July 03 2024 15:17:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:95bea772528d316c969a170e6206f3b05ac39413

142092 --> performance testing pass

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/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
Target: Unknown
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

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

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-04  7:11 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703151734.14458-1-stephen@networkplumber.org>
2024-07-03 14:50 ` qemudev
2024-07-03 14:54 ` qemudev
2024-07-03 15:18 ` checkpatch
2024-07-03 16:04 ` 0-day Robot
2024-07-04  3:52 ` dpdklab
2024-07-04  3:56 ` dpdklab
2024-07-04  4:01 ` dpdklab
2024-07-04  4:07 ` dpdklab
2024-07-04  4:10 ` dpdklab
2024-07-04  4:14 ` dpdklab
2024-07-04  4:17 ` dpdklab
2024-07-04  5:10 ` dpdklab
2024-07-04  5:35 ` |PENDING| " dpdklab
2024-07-04  5:43 ` dpdklab
2024-07-04  5:49 ` dpdklab
2024-07-04  5:56 ` dpdklab
2024-07-04  6:00 ` dpdklab
2024-07-04  6:01 ` dpdklab
2024-07-04  6:12 ` dpdklab
2024-07-04  6:12 ` dpdklab
2024-07-04  6:16 ` dpdklab
2024-07-04  6:21 ` dpdklab
2024-07-04  6:21 ` dpdklab
2024-07-04  6:28 ` dpdklab
2024-07-04  6:29 ` dpdklab
2024-07-04  6:33 ` dpdklab
2024-07-04  6:45 ` |SUCCESS| " dpdklab
2024-07-04  7:11 ` dpdklab [this message]
2024-07-04  7:16 ` dpdklab
2024-07-04  7:21 ` dpdklab
2024-07-04  7:26 ` dpdklab
2024-07-04  7:47 ` dpdklab
2024-07-04  7:54 ` dpdklab
2024-07-04  8:02 ` dpdklab
2024-07-04  8:37 ` dpdklab
2024-07-04 16:31 ` |PENDING| " dpdklab
2024-07-04 16:32 ` dpdklab
2024-07-04 16:35 ` dpdklab
2024-07-04 16:36 ` dpdklab
2024-07-04 16:36 ` dpdklab
2024-07-04 16:42 ` |SUCCESS| " dpdklab
2024-07-04 17:00 ` dpdklab
2024-07-04 17:52 ` |PENDING| " dpdklab
2024-07-04 17:56 ` dpdklab
2024-07-04 21:57 ` dpdklab
2024-07-04 21:58 ` dpdklab
2024-07-04 21:59 ` dpdklab
2024-07-04 22:04 ` dpdklab
2024-07-04 22:05 ` dpdklab
2024-07-04 22:08 ` dpdklab
2024-07-04 22:09 ` dpdklab
2024-07-04 22:11 ` dpdklab
2024-07-04 22:14 ` dpdklab
2024-07-04 22:14 ` dpdklab
2024-07-04 22:14 ` dpdklab
2024-07-04 22:15 ` dpdklab
2024-07-04 22:20 ` dpdklab
2024-07-04 22:21 ` dpdklab
2024-07-04 22:22 ` dpdklab
2024-07-04 22:23 ` dpdklab
2024-07-04 22:23 ` dpdklab
2024-07-04 22:24 ` dpdklab
2024-07-04 22:25 ` dpdklab
2024-07-04 22:25 ` dpdklab
2024-07-04 22:28 ` dpdklab
2024-07-04 22:32 ` dpdklab
2024-07-04 22:32 ` dpdklab
2024-07-04 22:33 ` dpdklab
2024-07-04 22:37 ` dpdklab
2024-07-04 22:40 ` dpdklab
2024-07-04 22:45 ` dpdklab
2024-07-04 22:45 ` dpdklab
2024-07-04 22:49 ` dpdklab
2024-07-04 22:54 ` dpdklab
2024-07-04 23:01 ` dpdklab
2024-07-04 23:01 ` dpdklab
2024-07-04 23:02 ` dpdklab
2024-07-04 23:04 ` dpdklab
2024-07-04 23:05 ` dpdklab
2024-07-04 23:07 ` dpdklab
2024-07-04 23:07 ` dpdklab
2024-07-04 23:10 ` |SUCCESS| " dpdklab
2024-07-04 23:12 ` |PENDING| " dpdklab
2024-07-04 23:13 ` dpdklab
2024-07-04 23:13 ` dpdklab
2024-07-04 23:17 ` dpdklab
2024-07-04 23:18 ` dpdklab
2024-07-04 23:19 ` dpdklab
2024-07-04 23:20 ` dpdklab
2024-07-04 23:22 ` dpdklab
2024-07-04 23:25 ` |SUCCESS| " dpdklab
2024-07-04 23:26 ` dpdklab
2024-07-04 23:28 ` |PENDING| " dpdklab
2024-07-04 23:30 ` dpdklab
2024-07-04 23:31 ` dpdklab
2024-07-04 23:35 ` dpdklab
2024-07-04 23:40 ` dpdklab
2024-07-04 23:43 ` dpdklab
2024-07-04 23:45 ` |SUCCESS| " dpdklab
2024-07-05  0:34 ` |PENDING| " dpdklab
2024-07-05  0:35 ` dpdklab
2024-07-05  5:36 ` |SUCCESS| " dpdklab
2024-07-05 18:12 ` dpdklab
2024-07-05 18:28 ` 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=66864b39.050a0220.edda6.8cbaSMTPIN_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).