From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129222 [PATCH] net/mlx5: forbid MPRQ restart
Date: Mon, 03 Jul 2023 14:59:04 -0700 (PDT) [thread overview]
Message-ID: <64a344a8.050a0220.692da.4908SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129222
_Performance Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Monday, July 03 2023 21:22:24
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:3cf3497213d2fe345729db3eadac2b543209213f
129222 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26939/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-03 21:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 21:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-05 1:40 dpdklab
2023-07-04 5:43 dpdklab
2023-07-04 5:32 dpdklab
2023-07-04 5:04 dpdklab
2023-07-04 4:34 dpdklab
2023-07-04 3:44 dpdklab
2023-07-03 22:21 dpdklab
2023-07-03 22:15 dpdklab
2023-07-03 22:15 dpdklab
2023-07-03 22:15 dpdklab
2023-07-03 22:14 dpdklab
2023-07-03 22:13 dpdklab
2023-07-03 22:13 dpdklab
2023-07-03 22:12 dpdklab
2023-07-03 22:12 dpdklab
2023-07-03 22:06 dpdklab
2023-07-03 22:03 dpdklab
2023-07-03 22:02 dpdklab
2023-07-03 22:00 dpdklab
2023-07-03 21:58 dpdklab
2023-07-03 21:57 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
2023-07-03 21:55 dpdklab
[not found] <20230703212224.2370414-1-akozyrev@nvidia.com>
2023-07-03 21:11 ` qemudev
2023-07-03 21:15 ` qemudev
2023-07-03 21:23 ` checkpatch
2023-07-03 22:19 ` 0-day Robot
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=64a344a8.050a0220.692da.4908SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).