From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142677 [PATCH] [v2] doc: document mlx5 HWS actions order
Date: Wed, 24 Jul 2024 04:14:22 -0700 (PDT) [thread overview]
Message-ID: <66a0e20e.050a0220.c21bd.559fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240724073617.132973-1-mkashani@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142677
_Performance Testing PASS_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Wednesday, July 24 2024 07:36:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142677 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#170342
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.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.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/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.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30603/
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-24 11:23 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240724073617.132973-1-mkashani@nvidia.com>
2024-07-24 7:32 ` |SUCCESS| pw142677 [PATCH v2] " qemudev
2024-07-24 7:36 ` qemudev
2024-07-24 8:00 ` checkpatch
2024-07-24 9:03 ` 0-day Robot
2024-07-24 9:49 ` |PENDING| pw142677 [PATCH] [v2] " dpdklab
2024-07-24 9:53 ` dpdklab
2024-07-24 9:56 ` |SUCCESS| " dpdklab
2024-07-24 10:03 ` dpdklab
2024-07-24 10:05 ` dpdklab
2024-07-24 10:06 ` dpdklab
2024-07-24 10:14 ` dpdklab
2024-07-24 10:20 ` dpdklab
2024-07-24 10:43 ` dpdklab
2024-07-24 10:49 ` dpdklab
2024-07-24 10:54 ` dpdklab
2024-07-24 10:59 ` dpdklab
2024-07-24 11:14 ` dpdklab [this message]
2024-07-24 11:22 ` dpdklab
2024-07-24 11:26 ` |PENDING| " dpdklab
2024-07-24 11:28 ` dpdklab
2024-07-24 11:28 ` |SUCCESS| " dpdklab
2024-07-24 11:29 ` |PENDING| " dpdklab
2024-07-24 11:37 ` dpdklab
2024-07-24 11:42 ` dpdklab
2024-07-24 11:43 ` dpdklab
2024-07-24 11:43 ` dpdklab
2024-07-24 11:46 ` dpdklab
2024-07-24 11:47 ` |SUCCESS| " dpdklab
2024-07-24 11:48 ` |PENDING| " dpdklab
2024-07-24 11:49 ` dpdklab
2024-07-24 11:50 ` dpdklab
2024-07-24 11:50 ` dpdklab
2024-07-24 11:56 ` dpdklab
2024-07-24 11:57 ` dpdklab
2024-07-24 11:57 ` |SUCCESS| " dpdklab
2024-07-24 12:01 ` dpdklab
2024-07-24 12:45 ` |PENDING| " dpdklab
2024-07-24 12:55 ` dpdklab
2024-07-24 12:55 ` dpdklab
2024-07-24 13:03 ` dpdklab
2024-07-24 13:06 ` |SUCCESS| " dpdklab
2024-07-24 13:07 ` dpdklab
2024-07-24 13:16 ` |PENDING| " dpdklab
2024-07-24 13:16 ` dpdklab
2024-07-24 13:28 ` dpdklab
2024-07-24 14:21 ` dpdklab
2024-07-24 14:25 ` dpdklab
2024-07-24 14:28 ` dpdklab
2024-07-24 14:29 ` dpdklab
2024-07-24 14:30 ` dpdklab
2024-07-24 14:31 ` dpdklab
2024-07-24 14:36 ` dpdklab
2024-07-24 14:37 ` dpdklab
2024-07-24 14:38 ` dpdklab
2024-07-24 14:39 ` dpdklab
2024-07-24 14:42 ` dpdklab
2024-07-24 14:51 ` dpdklab
2024-07-24 14:54 ` dpdklab
2024-07-24 14:57 ` dpdklab
2024-07-24 15:03 ` dpdklab
2024-07-24 15:03 ` dpdklab
2024-07-24 15:05 ` dpdklab
2024-07-24 15:07 ` dpdklab
2024-07-24 15:09 ` dpdklab
2024-07-24 15:09 ` dpdklab
2024-07-24 15:10 ` dpdklab
2024-07-24 15:11 ` dpdklab
2024-07-24 15:13 ` dpdklab
2024-07-24 15:15 ` dpdklab
2024-07-24 15:15 ` dpdklab
2024-07-24 15:17 ` dpdklab
2024-07-24 15:18 ` dpdklab
2024-07-24 15:18 ` dpdklab
2024-07-24 15:21 ` dpdklab
2024-07-24 15:22 ` dpdklab
2024-07-24 15:22 ` dpdklab
2024-07-24 15:24 ` dpdklab
2024-07-24 15:24 ` dpdklab
2024-07-24 15:30 ` dpdklab
2024-07-24 15:33 ` dpdklab
2024-07-24 15:33 ` dpdklab
2024-07-24 15:35 ` dpdklab
2024-07-24 15:35 ` dpdklab
2024-07-24 15:36 ` dpdklab
2024-07-24 15:36 ` dpdklab
2024-07-24 15:37 ` dpdklab
2024-07-24 15:37 ` dpdklab
2024-07-24 15:37 ` dpdklab
2024-07-24 15:38 ` dpdklab
2024-07-24 15:39 ` dpdklab
2024-07-24 15:39 ` dpdklab
2024-07-24 15:42 ` dpdklab
2024-07-24 15:43 ` |SUCCESS| " dpdklab
2024-07-24 15:43 ` dpdklab
2024-07-24 15:44 ` dpdklab
2024-07-24 15:44 ` |PENDING| " dpdklab
2024-07-24 15:45 ` dpdklab
2024-07-24 15:46 ` dpdklab
2024-07-24 15:46 ` dpdklab
2024-07-24 15:47 ` dpdklab
2024-07-24 15:48 ` dpdklab
2024-07-24 15:52 ` |SUCCESS| " dpdklab
2024-07-24 15:53 ` |PENDING| " dpdklab
2024-07-24 15:53 ` dpdklab
2024-07-24 16:04 ` dpdklab
2024-07-24 16:05 ` |SUCCESS| " dpdklab
2024-07-24 16:07 ` dpdklab
2024-07-24 16:07 ` |PENDING| " dpdklab
2024-07-24 16:09 ` dpdklab
2024-07-24 16:11 ` dpdklab
2024-07-24 16:11 ` dpdklab
2024-07-24 16:21 ` dpdklab
2024-07-24 16:22 ` |SUCCESS| " dpdklab
2024-07-24 16:23 ` dpdklab
2024-07-25 18:47 ` 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=66a0e20e.050a0220.c21bd.559fSMTPIN_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).