From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140400 [PATCH] net/mlx5: break resource release forever
Date: Thu, 30 May 2024 00:52:48 -0700 (PDT) [thread overview]
Message-ID: <66583050.170a0220.3059c.6de2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529214632.1980988-1-akozyrev@nvidia.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/140400
_Performance Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Wednesday, May 29 2024 21:46:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5d185b9afaca3c98d8fd779e97d83e571660f4cf
140400 --> performance testing pass
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
Target: Unknown
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30042/
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-05-30 7:52 UTC|newest]
Thread overview: 172+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240529214632.1980988-1-akozyrev@nvidia.com>
2024-05-29 21:20 ` |SUCCESS| pw140400 [PATCH] net/mlx5: break resource release forever loop qemudev
2024-05-29 21:24 ` qemudev
2024-05-29 21:47 ` checkpatch
2024-05-29 22:43 ` |FAILURE| " 0-day Robot
2024-05-30 0:33 ` |SUCCESS| pw140400 [PATCH] net/mlx5: break resource release forever dpdklab
2024-05-30 0:35 ` dpdklab
2024-05-30 0:59 ` dpdklab
2024-05-30 1:22 ` dpdklab
2024-05-30 1:30 ` dpdklab
2024-05-30 1:36 ` dpdklab
2024-05-30 1:40 ` dpdklab
2024-05-30 1:41 ` dpdklab
2024-05-30 1:42 ` dpdklab
2024-05-30 1:43 ` |FAILURE| " dpdklab
2024-05-30 1:43 ` dpdklab
2024-05-30 1:43 ` dpdklab
2024-05-30 1:43 ` |SUCCESS| " dpdklab
2024-05-30 1:43 ` dpdklab
2024-05-30 1:43 ` dpdklab
2024-05-30 1:44 ` dpdklab
2024-05-30 1:44 ` |FAILURE| " dpdklab
2024-05-30 1:44 ` |SUCCESS| " dpdklab
2024-05-30 1:44 ` dpdklab
2024-05-30 1:44 ` |FAILURE| " dpdklab
2024-05-30 1:44 ` dpdklab
2024-05-30 1:44 ` |SUCCESS| " dpdklab
2024-05-30 1:45 ` |FAILURE| " dpdklab
2024-05-30 1:45 ` |SUCCESS| " dpdklab
2024-05-30 1:45 ` |FAILURE| " dpdklab
2024-05-30 1:45 ` dpdklab
2024-05-30 1:45 ` |SUCCESS| " dpdklab
2024-05-30 1:45 ` dpdklab
2024-05-30 1:45 ` dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` |FAILURE| " dpdklab
2024-05-30 1:46 ` dpdklab
2024-05-30 1:46 ` |SUCCESS| " dpdklab
2024-05-30 1:47 ` dpdklab
2024-05-30 1:47 ` |FAILURE| " dpdklab
2024-05-30 1:48 ` |SUCCESS| " dpdklab
2024-05-30 1:49 ` dpdklab
2024-05-30 1:49 ` dpdklab
2024-05-30 1:54 ` |FAILURE| " dpdklab
2024-05-30 1:54 ` |SUCCESS| " dpdklab
2024-05-30 1:54 ` dpdklab
2024-05-30 1:54 ` |FAILURE| " dpdklab
2024-05-30 1:55 ` |SUCCESS| " dpdklab
2024-05-30 2:05 ` dpdklab
2024-05-30 2:06 ` dpdklab
2024-05-30 2:07 ` |FAILURE| " dpdklab
2024-05-30 2:07 ` |SUCCESS| " dpdklab
2024-05-30 2:07 ` |FAILURE| " dpdklab
2024-05-30 2:08 ` |SUCCESS| " dpdklab
2024-05-30 2:08 ` dpdklab
2024-05-30 2:11 ` dpdklab
2024-05-30 2:12 ` dpdklab
2024-05-30 2:13 ` |FAILURE| " dpdklab
2024-05-30 2:15 ` |SUCCESS| " dpdklab
2024-05-30 2:16 ` dpdklab
2024-05-30 2:18 ` |FAILURE| " dpdklab
2024-05-30 2:20 ` |SUCCESS| " dpdklab
2024-05-30 2:22 ` dpdklab
2024-05-30 2:39 ` dpdklab
2024-05-30 2:51 ` |FAILURE| " dpdklab
2024-05-30 2:54 ` |SUCCESS| " dpdklab
2024-05-30 4:36 ` |FAILURE| " dpdklab
2024-05-30 7:52 ` dpdklab [this message]
2024-05-30 7:52 ` |SUCCESS| " dpdklab
2024-05-30 7:59 ` dpdklab
2024-05-30 15:23 ` dpdklab
2024-05-30 15:23 ` dpdklab
2024-05-30 15:35 ` dpdklab
2024-06-01 7:08 ` dpdklab
2024-06-01 7:08 ` dpdklab
2024-06-01 7:09 ` dpdklab
2024-06-01 7:11 ` dpdklab
2024-06-01 7:11 ` dpdklab
2024-06-01 7:57 ` dpdklab
2024-06-01 8:07 ` dpdklab
2024-06-01 9:19 ` dpdklab
2024-06-01 9:25 ` dpdklab
2024-06-01 10:12 ` dpdklab
2024-06-01 10:13 ` dpdklab
2024-06-01 10:19 ` dpdklab
2024-06-01 10:20 ` dpdklab
2024-06-01 10:22 ` dpdklab
2024-06-01 10:23 ` dpdklab
2024-06-01 10:23 ` dpdklab
2024-06-01 10:25 ` dpdklab
2024-06-01 10:26 ` dpdklab
2024-06-01 10:26 ` dpdklab
2024-06-01 10:27 ` dpdklab
2024-06-01 10:28 ` dpdklab
2024-06-01 10:39 ` dpdklab
2024-06-01 12:01 ` dpdklab
2024-06-01 12:10 ` dpdklab
2024-06-01 12:11 ` dpdklab
2024-06-01 12:11 ` dpdklab
2024-06-01 12:12 ` dpdklab
2024-06-01 12:12 ` dpdklab
2024-06-01 13:43 ` dpdklab
2024-06-01 14:22 ` |FAILURE| " dpdklab
2024-06-01 14:35 ` dpdklab
2024-06-01 14:40 ` dpdklab
2024-06-01 14:41 ` dpdklab
2024-06-01 14:42 ` dpdklab
2024-06-01 14:43 ` dpdklab
2024-06-01 14:45 ` dpdklab
2024-06-01 14:56 ` dpdklab
2024-06-01 14:58 ` dpdklab
2024-06-01 15:01 ` dpdklab
2024-06-01 15:02 ` dpdklab
2024-06-01 15:06 ` dpdklab
2024-06-01 15:27 ` dpdklab
2024-06-01 15:29 ` dpdklab
2024-06-01 15:31 ` dpdklab
2024-06-01 15:33 ` dpdklab
2024-06-01 15:34 ` dpdklab
2024-06-01 15:34 ` dpdklab
2024-06-01 15:35 ` dpdklab
2024-06-01 15:36 ` dpdklab
2024-06-01 15:36 ` dpdklab
2024-06-01 15:38 ` dpdklab
2024-06-01 15:45 ` dpdklab
2024-06-01 16:04 ` dpdklab
2024-06-01 16:06 ` dpdklab
2024-06-01 16:08 ` dpdklab
2024-06-01 16:08 ` dpdklab
2024-06-01 16:11 ` dpdklab
2024-06-01 16:12 ` dpdklab
2024-06-01 16:20 ` dpdklab
2024-06-01 16:21 ` dpdklab
2024-06-01 16:21 ` dpdklab
2024-06-01 16:22 ` dpdklab
2024-06-01 16:22 ` dpdklab
2024-06-01 16:23 ` dpdklab
2024-06-01 16:23 ` dpdklab
2024-06-01 16:24 ` |SUCCESS| " dpdklab
2024-06-01 16:25 ` |FAILURE| " dpdklab
2024-06-01 16:29 ` dpdklab
2024-06-01 16:30 ` dpdklab
2024-06-01 16:31 ` dpdklab
2024-06-01 16:31 ` dpdklab
2024-06-01 16:32 ` |SUCCESS| " dpdklab
2024-06-01 16:34 ` dpdklab
2024-06-01 16:35 ` dpdklab
2024-06-01 16:36 ` dpdklab
2024-06-01 16:37 ` dpdklab
2024-06-01 16:38 ` dpdklab
2024-06-01 16:39 ` |FAILURE| " dpdklab
2024-06-01 16:43 ` |SUCCESS| " dpdklab
2024-06-01 16:52 ` |FAILURE| " dpdklab
2024-06-01 16:53 ` dpdklab
2024-06-01 16:54 ` dpdklab
2024-06-01 16:55 ` dpdklab
2024-06-01 16:56 ` dpdklab
2024-06-01 16:57 ` dpdklab
2024-06-01 16:58 ` dpdklab
2024-06-01 17:34 ` dpdklab
2024-06-01 17:48 ` |SUCCESS| " dpdklab
2024-06-01 17:49 ` dpdklab
2024-06-01 18:05 ` dpdklab
2024-06-01 18:07 ` |FAILURE| " dpdklab
2024-06-01 18:09 ` |SUCCESS| " dpdklab
2024-06-01 18:56 ` dpdklab
2024-06-01 21:07 ` |FAILURE| " dpdklab
2024-06-01 21:20 ` dpdklab
2024-06-02 1:39 ` |SUCCESS| " 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=66583050.170a0220.3059c.6de2SMTPIN_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).