From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142500-142501 [PATCH] [3/3] net/mlx5: fix RSS and queue
Date: Thu, 18 Jul 2024 04:36:36 -0700 (PDT) [thread overview]
Message-ID: <6698fe44.c80a0220.771a4.1193SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240718095717.290960-4-dsosnowski@nvidia.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142501
_Performance Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Thursday, July 18 2024 09:57:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0c31131307df0ce6c8d682dc5c967394196b24f7
142500-142501 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#168801
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.6% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30552/
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-18 11:36 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240718095717.290960-4-dsosnowski@nvidia.com>
2024-07-18 9:31 ` |SUCCESS| pw142500-142501 [PATCH 3/3] net/mlx5: fix RSS and queue action validation qemudev
2024-07-18 9:36 ` qemudev
2024-07-18 9:59 ` |SUCCESS| pw142501 " checkpatch
2024-07-18 10:43 ` 0-day Robot
2024-07-18 11:12 ` |SUCCESS| pw142500-142501 [PATCH] [3/3] net/mlx5: fix RSS and queue dpdklab
2024-07-18 11:16 ` dpdklab
2024-07-18 11:17 ` |PENDING| " dpdklab
2024-07-18 11:17 ` dpdklab
2024-07-18 11:20 ` |SUCCESS| " dpdklab
2024-07-18 11:21 ` |PENDING| " dpdklab
2024-07-18 11:22 ` dpdklab
2024-07-18 11:22 ` dpdklab
2024-07-18 11:23 ` dpdklab
2024-07-18 11:25 ` |SUCCESS| " dpdklab
2024-07-18 11:26 ` dpdklab
2024-07-18 11:28 ` |PENDING| " dpdklab
2024-07-18 11:29 ` dpdklab
2024-07-18 11:29 ` |SUCCESS| " dpdklab
2024-07-18 11:32 ` |PENDING| " dpdklab
2024-07-18 11:33 ` |SUCCESS| " dpdklab
2024-07-18 11:33 ` dpdklab
2024-07-18 11:33 ` |PENDING| " dpdklab
2024-07-18 11:34 ` |SUCCESS| " dpdklab
2024-07-18 11:34 ` dpdklab
2024-07-18 11:36 ` dpdklab [this message]
2024-07-18 11:37 ` |PENDING| " dpdklab
2024-07-18 11:40 ` |SUCCESS| " dpdklab
2024-07-18 11:40 ` |PENDING| " dpdklab
2024-07-18 11:43 ` dpdklab
2024-07-18 11:43 ` dpdklab
2024-07-18 11:43 ` dpdklab
2024-07-18 11:43 ` dpdklab
2024-07-18 11:45 ` dpdklab
2024-07-18 11:46 ` dpdklab
2024-07-18 11:49 ` dpdklab
2024-07-18 11:53 ` dpdklab
2024-07-18 11:54 ` dpdklab
2024-07-18 11:56 ` dpdklab
2024-07-18 11:59 ` dpdklab
2024-07-18 12:00 ` |SUCCESS| " dpdklab
2024-07-18 12:01 ` |PENDING| " dpdklab
2024-07-18 12:02 ` dpdklab
2024-07-18 12:02 ` dpdklab
2024-07-18 12:03 ` dpdklab
2024-07-18 12:03 ` dpdklab
2024-07-18 12:05 ` dpdklab
2024-07-18 12:07 ` dpdklab
2024-07-18 12:09 ` dpdklab
2024-07-18 12:09 ` dpdklab
2024-07-18 12:11 ` dpdklab
2024-07-18 12:13 ` dpdklab
2024-07-18 12:14 ` dpdklab
2024-07-18 12:15 ` dpdklab
2024-07-18 12:16 ` dpdklab
2024-07-18 12:17 ` dpdklab
2024-07-18 12:20 ` dpdklab
2024-07-18 12:20 ` dpdklab
2024-07-18 12:21 ` dpdklab
2024-07-18 12:22 ` dpdklab
2024-07-18 12:23 ` dpdklab
2024-07-18 12:24 ` |SUCCESS| " dpdklab
2024-07-18 12:24 ` |PENDING| " dpdklab
2024-07-18 12:25 ` dpdklab
2024-07-18 12:25 ` dpdklab
2024-07-18 12:26 ` dpdklab
2024-07-18 12:26 ` dpdklab
2024-07-18 12:27 ` dpdklab
2024-07-18 12:27 ` dpdklab
2024-07-18 12:30 ` dpdklab
2024-07-18 12:30 ` |SUCCESS| " dpdklab
2024-07-18 12:30 ` |PENDING| " dpdklab
2024-07-18 12:31 ` dpdklab
2024-07-18 12:32 ` dpdklab
2024-07-18 12:34 ` dpdklab
2024-07-18 12:34 ` dpdklab
2024-07-18 12:34 ` dpdklab
2024-07-18 12:39 ` dpdklab
2024-07-18 12:43 ` dpdklab
2024-07-18 12:44 ` dpdklab
2024-07-18 12:47 ` dpdklab
2024-07-18 12:48 ` dpdklab
2024-07-18 12:53 ` dpdklab
2024-07-18 12:53 ` dpdklab
2024-07-18 12:54 ` dpdklab
2024-07-18 12:55 ` |SUCCESS| " dpdklab
2024-07-18 12:56 ` |PENDING| " dpdklab
2024-07-18 13:00 ` dpdklab
2024-07-18 13:02 ` dpdklab
2024-07-18 13:05 ` dpdklab
2024-07-18 13:05 ` dpdklab
2024-07-18 13:06 ` dpdklab
2024-07-18 13:07 ` dpdklab
2024-07-18 13:07 ` dpdklab
2024-07-18 13:07 ` dpdklab
2024-07-18 13:11 ` dpdklab
2024-07-18 13:12 ` dpdklab
2024-07-18 13:14 ` dpdklab
2024-07-18 13:14 ` dpdklab
2024-07-18 13:15 ` dpdklab
2024-07-18 13:19 ` |SUCCESS| " dpdklab
2024-07-18 13:19 ` |PENDING| " dpdklab
2024-07-18 13:22 ` |SUCCESS| " dpdklab
2024-07-18 13:23 ` |PENDING| " dpdklab
2024-07-18 13:26 ` |SUCCESS| " dpdklab
2024-07-18 13:27 ` |PENDING| " dpdklab
2024-07-18 13:32 ` dpdklab
2024-07-18 13:42 ` dpdklab
2024-07-18 13:45 ` |SUCCESS| " dpdklab
2024-07-18 13:48 ` dpdklab
2024-07-18 13:52 ` dpdklab
2024-07-18 13:53 ` dpdklab
2024-07-18 21: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=6698fe44.c80a0220.771a4.1193SMTPIN_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).