From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142821-142837 [PATCH] [17/17] net/dpaa: improve dpaa err
Date: Thu, 01 Aug 2024 16:02:26 -0700 (PDT) [thread overview]
Message-ID: <66ac1402.170a0220.2d616f.1b5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801105313.630280-18-hemant.agrawal@nxp.com>
Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/142837
_Performance Testing pending_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Thursday, August 01 2024 10:53:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:37ce4c84c0f23c3989bc7ae19e03a4593cec94e5
142821-142837 --> performance testing pending
Upstream job id: Template-DTS-Pipeline#172510
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -3.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
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/30696/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-08-01 23:02 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801105313.630280-18-hemant.agrawal@nxp.com>
2024-08-01 10:35 ` |SUCCESS| pw142821-142837 [PATCH 17/17] net/dpaa: improve dpaa errata A010022 handling qemudev
2024-08-01 10:40 ` qemudev
2024-08-01 10:58 ` |SUCCESS| pw142837 " checkpatch
2024-08-01 15:02 ` 0-day Robot
2024-08-01 20:15 ` |SUCCESS| pw142821-142837 [PATCH] [17/17] net/dpaa: improve dpaa err dpdklab
2024-08-01 20:53 ` |PENDING| " dpdklab
2024-08-01 21:04 ` dpdklab
2024-08-01 21:06 ` |SUCCESS| " dpdklab
2024-08-01 21:17 ` dpdklab
2024-08-01 21:38 ` dpdklab
2024-08-01 23:02 ` dpdklab [this message]
2024-08-01 23:05 ` |PENDING| " dpdklab
2024-08-01 23:09 ` dpdklab
2024-08-01 23:10 ` |SUCCESS| " dpdklab
2024-08-01 23:19 ` |PENDING| " dpdklab
2024-08-01 23:20 ` dpdklab
2024-08-01 23:21 ` |SUCCESS| " dpdklab
2024-08-01 23:21 ` |PENDING| " dpdklab
2024-08-01 23:23 ` dpdklab
2024-08-01 23:25 ` |SUCCESS| " dpdklab
2024-08-01 23:26 ` dpdklab
2024-08-01 23:27 ` dpdklab
2024-08-01 23:29 ` |PENDING| " dpdklab
2024-08-01 23:45 ` |SUCCESS| " dpdklab
2024-08-01 23:46 ` |PENDING| " dpdklab
2024-08-01 23:46 ` dpdklab
2024-08-01 23:47 ` dpdklab
2024-08-01 23:48 ` dpdklab
2024-08-01 23:49 ` dpdklab
2024-08-01 23:50 ` |SUCCESS| " dpdklab
2024-08-01 23:51 ` |PENDING| " dpdklab
2024-08-01 23:51 ` dpdklab
2024-08-01 23:52 ` dpdklab
2024-08-01 23:54 ` dpdklab
2024-08-01 23:57 ` dpdklab
2024-08-02 0:01 ` dpdklab
2024-08-02 0:08 ` dpdklab
2024-08-02 0:15 ` dpdklab
2024-08-02 0:16 ` dpdklab
2024-08-02 0:20 ` |SUCCESS| " dpdklab
2024-08-02 0:25 ` dpdklab
2024-08-02 0:50 ` dpdklab
2024-08-02 1:10 ` dpdklab
2024-08-02 1:16 ` |PENDING| " dpdklab
2024-08-02 1:18 ` dpdklab
2024-08-02 1:22 ` dpdklab
2024-08-02 1:24 ` dpdklab
2024-08-02 1:28 ` dpdklab
2024-08-02 1:29 ` dpdklab
2024-08-02 1:29 ` dpdklab
2024-08-02 1:32 ` dpdklab
2024-08-02 1:34 ` dpdklab
2024-08-02 1:34 ` dpdklab
2024-08-02 1:36 ` dpdklab
2024-08-02 1:37 ` dpdklab
2024-08-02 1:40 ` dpdklab
2024-08-02 1:43 ` dpdklab
2024-08-02 1:43 ` dpdklab
2024-08-02 1:43 ` dpdklab
2024-08-02 1:44 ` dpdklab
2024-08-02 1:44 ` dpdklab
2024-08-02 1:47 ` dpdklab
2024-08-02 1:48 ` dpdklab
2024-08-02 1:52 ` dpdklab
2024-08-02 1:54 ` dpdklab
2024-08-02 1:55 ` dpdklab
2024-08-02 1:59 ` dpdklab
2024-08-02 1:59 ` dpdklab
2024-08-02 2:00 ` dpdklab
2024-08-02 2:01 ` dpdklab
2024-08-02 2:04 ` dpdklab
2024-08-02 2:07 ` dpdklab
2024-08-02 2:07 ` dpdklab
2024-08-02 2:08 ` dpdklab
2024-08-02 2:10 ` dpdklab
2024-08-02 2:11 ` dpdklab
2024-08-02 2:12 ` dpdklab
2024-08-02 2:12 ` dpdklab
2024-08-02 2:13 ` dpdklab
2024-08-02 2:14 ` dpdklab
2024-08-02 2:14 ` dpdklab
2024-08-02 2:15 ` dpdklab
2024-08-02 2:17 ` dpdklab
2024-08-02 2:19 ` dpdklab
2024-08-02 2:22 ` dpdklab
2024-08-02 2:28 ` dpdklab
2024-08-02 2:30 ` |SUCCESS| " dpdklab
2024-08-02 2:38 ` dpdklab
2024-08-02 2:41 ` |PENDING| " dpdklab
2024-08-02 2:52 ` dpdklab
2024-08-02 2:53 ` dpdklab
2024-08-02 2:55 ` dpdklab
2024-08-02 2:57 ` dpdklab
2024-08-02 2:59 ` dpdklab
2024-08-02 3:03 ` dpdklab
2024-08-02 3:04 ` dpdklab
2024-08-02 3:04 ` dpdklab
2024-08-02 3:05 ` dpdklab
2024-08-02 3:13 ` dpdklab
2024-08-02 3:15 ` dpdklab
2024-08-02 3:18 ` dpdklab
2024-08-02 3:20 ` dpdklab
2024-08-02 3:20 ` dpdklab
2024-08-02 3:21 ` dpdklab
2024-08-02 3:21 ` dpdklab
2024-08-02 3:22 ` dpdklab
2024-08-02 3:23 ` |SUCCESS| " dpdklab
2024-08-02 3:23 ` |PENDING| " dpdklab
2024-08-02 3:24 ` dpdklab
2024-08-02 3:24 ` |SUCCESS| " dpdklab
2024-08-02 3:31 ` dpdklab
2024-08-03 2:32 ` dpdklab
2024-08-06 4:42 ` dpdklab
2024-08-06 4:50 ` dpdklab
2024-08-06 5:05 ` 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=66ac1402.170a0220.2d616f.1b5eSMTPIN_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).