From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142223 [PATCH] [v3] eal/common: fix inconsistent represe
Date: Mon, 08 Jul 2024 19:10:03 -0700 (PDT) [thread overview]
Message-ID: <668c9bfb.050a0220.41c20.28b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240708165145.1405107-1-shperetz@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/142223
_Performance Testing pending_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Monday, July 08 2024 16:51:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e6bfd9676109f904b4f263402e77105fdca8e67c
142223 --> performance testing pending
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/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.4% |
+------------+---------+----------+-------------+------------------------------+
| 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
Target: Unknown
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/30460/
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-07-09 2:10 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240708165145.1405107-1-shperetz@nvidia.com>
2024-07-08 16:26 ` |SUCCESS| pw142223 [PATCH v3] eal/common: fix inconsistent representation of PCI numbers qemudev
2024-07-08 16:30 ` qemudev
2024-07-08 16:52 ` checkpatch
2024-07-08 17:43 ` 0-day Robot
2024-07-09 0:28 ` |PENDING| pw142223 [PATCH] [v3] eal/common: fix inconsistent represe dpdklab
2024-07-09 0:40 ` |SUCCESS| " dpdklab
2024-07-09 1:06 ` |PENDING| " dpdklab
2024-07-09 1:09 ` |SUCCESS| " dpdklab
2024-07-09 1:14 ` |PENDING| " dpdklab
2024-07-09 1:14 ` |SUCCESS| " dpdklab
2024-07-09 1:28 ` dpdklab
2024-07-09 1:29 ` dpdklab
2024-07-09 1:34 ` |PENDING| " dpdklab
2024-07-09 1:41 ` dpdklab
2024-07-09 1:42 ` dpdklab
2024-07-09 1:44 ` dpdklab
2024-07-09 1:45 ` dpdklab
2024-07-09 1:49 ` dpdklab
2024-07-09 1:52 ` dpdklab
2024-07-09 1:55 ` dpdklab
2024-07-09 1:59 ` dpdklab
2024-07-09 2:02 ` dpdklab
2024-07-09 2:03 ` dpdklab
2024-07-09 2:05 ` dpdklab
2024-07-09 2:10 ` dpdklab [this message]
2024-07-09 2:12 ` dpdklab
2024-07-09 2:18 ` |SUCCESS| " dpdklab
2024-07-09 2:20 ` |PENDING| " dpdklab
2024-07-09 2:21 ` dpdklab
2024-07-09 2:24 ` |SUCCESS| " dpdklab
2024-07-09 2:53 ` dpdklab
2024-07-09 3:48 ` |PENDING| " dpdklab
2024-07-09 3:50 ` dpdklab
2024-07-09 4:02 ` dpdklab
2024-07-09 4:02 ` dpdklab
2024-07-09 4:04 ` dpdklab
2024-07-09 4:05 ` dpdklab
2024-07-09 4:07 ` |SUCCESS| " dpdklab
2024-07-09 4:08 ` dpdklab
2024-07-09 4:23 ` dpdklab
2024-07-09 4:31 ` |PENDING| " dpdklab
2024-07-09 5:22 ` dpdklab
2024-07-09 5:34 ` dpdklab
2024-07-09 5:45 ` dpdklab
2024-07-09 5:46 ` dpdklab
2024-07-09 5:47 ` dpdklab
2024-07-09 5:51 ` dpdklab
2024-07-09 5:58 ` dpdklab
2024-07-09 6:02 ` dpdklab
2024-07-09 6:04 ` dpdklab
2024-07-09 6:13 ` dpdklab
2024-07-09 6:15 ` dpdklab
2024-07-09 6:15 ` dpdklab
2024-07-09 6:18 ` dpdklab
2024-07-09 6:23 ` dpdklab
2024-07-09 6:28 ` dpdklab
2024-07-09 6:34 ` dpdklab
2024-07-09 6:35 ` dpdklab
2024-07-09 6:37 ` |SUCCESS| " dpdklab
2024-07-09 7:29 ` |PENDING| " dpdklab
2024-07-09 7:38 ` dpdklab
2024-07-09 8:05 ` dpdklab
2024-07-09 8:11 ` dpdklab
2024-07-09 8:19 ` dpdklab
2024-07-09 8:19 ` dpdklab
2024-07-09 8:22 ` dpdklab
2024-07-09 8:26 ` dpdklab
2024-07-09 8:29 ` dpdklab
2024-07-09 8:34 ` dpdklab
2024-07-09 8:34 ` dpdklab
2024-07-09 8:40 ` dpdklab
2024-07-09 8:40 ` dpdklab
2024-07-09 8:44 ` dpdklab
2024-07-09 8:44 ` dpdklab
2024-07-09 8:45 ` dpdklab
2024-07-09 8:46 ` dpdklab
2024-07-09 8:59 ` dpdklab
2024-07-09 9:03 ` dpdklab
2024-07-09 9:04 ` dpdklab
2024-07-09 9:04 ` dpdklab
2024-07-09 9:06 ` dpdklab
2024-07-09 9:12 ` dpdklab
2024-07-09 9:16 ` |SUCCESS| " dpdklab
2024-07-09 9:21 ` |PENDING| " dpdklab
2024-07-09 9:23 ` dpdklab
2024-07-09 9:35 ` dpdklab
2024-07-09 9:38 ` dpdklab
2024-07-09 9:41 ` dpdklab
2024-07-09 9:49 ` dpdklab
2024-07-09 10:03 ` dpdklab
2024-07-09 10:08 ` dpdklab
2024-07-09 10:10 ` dpdklab
2024-07-09 10:17 ` dpdklab
2024-07-09 10:37 ` dpdklab
2024-07-09 10:37 ` dpdklab
2024-07-09 10:45 ` dpdklab
2024-07-09 11:01 ` dpdklab
2024-07-09 11:06 ` dpdklab
2024-07-09 11:07 ` dpdklab
2024-07-09 11:14 ` dpdklab
2024-07-09 11:18 ` dpdklab
2024-07-09 11:30 ` dpdklab
2024-07-09 11:37 ` dpdklab
2024-07-09 11:39 ` dpdklab
2024-07-09 11:44 ` dpdklab
2024-07-09 11:47 ` dpdklab
2024-07-09 11:49 ` dpdklab
2024-07-09 12:09 ` dpdklab
2024-07-09 12:17 ` |SUCCESS| " dpdklab
2024-07-09 12:51 ` dpdklab
2024-07-09 14:04 ` dpdklab
2024-07-09 21:05 ` dpdklab
2024-07-09 22:30 ` dpdklab
2024-07-09 22:52 ` dpdklab
2024-07-13 17:46 ` dpdklab
2024-07-14 9:37 ` dpdklab
2024-07-14 16:11 ` dpdklab
2024-07-15 6:58 ` dpdklab
2024-07-15 7: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=668c9bfb.050a0220.41c20.28b9SMTPIN_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).