From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132580 [PATCH] net/mlx5: fix MPRQ stride size check
Date: Thu, 12 Oct 2023 19:41:45 -0700 (PDT) [thread overview]
Message-ID: <6528ae69.050a0220.fcbfe.9d45SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/132580
_Performance Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thursday, October 12 2023 16:34:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:77f913752a55c0262bfda99a1b69ca0bd804c6c7
132580 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27916/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-13 2:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 2:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 15:19 dpdklab
2023-10-13 6:20 dpdklab
2023-10-13 4:01 dpdklab
2023-10-13 3:57 dpdklab
2023-10-13 3:29 dpdklab
2023-10-13 3:06 dpdklab
2023-10-13 3:05 dpdklab
2023-10-13 3:05 dpdklab
2023-10-13 3:04 dpdklab
2023-10-13 3:04 dpdklab
2023-10-13 3:01 dpdklab
2023-10-13 2:59 dpdklab
2023-10-13 2:58 dpdklab
2023-10-13 2:55 dpdklab
2023-10-13 2:54 dpdklab
2023-10-13 2:54 dpdklab
2023-10-13 2:53 dpdklab
2023-10-13 2:53 dpdklab
2023-10-13 2:53 dpdklab
2023-10-13 2:53 dpdklab
2023-10-13 2:52 dpdklab
2023-10-13 2:52 dpdklab
2023-10-13 2:52 dpdklab
2023-10-13 2:51 dpdklab
2023-10-13 2:51 dpdklab
2023-10-13 2:50 dpdklab
2023-10-13 2:50 dpdklab
2023-10-13 2:50 dpdklab
2023-10-13 2:50 dpdklab
2023-10-13 2:49 dpdklab
2023-10-13 2:49 dpdklab
2023-10-13 2:49 dpdklab
2023-10-13 2:49 dpdklab
2023-10-13 2:49 dpdklab
2023-10-13 2:48 dpdklab
2023-10-13 2:48 dpdklab
2023-10-13 2:47 dpdklab
2023-10-13 2:47 dpdklab
2023-10-13 2:46 dpdklab
2023-10-13 2:46 dpdklab
2023-10-13 2:46 dpdklab
2023-10-13 2:46 dpdklab
2023-10-13 2:45 dpdklab
2023-10-13 2:45 dpdklab
2023-10-13 2:45 dpdklab
2023-10-13 2:40 dpdklab
[not found] <20231012163433.164254-1-akozyrev@nvidia.com>
2023-10-12 16:16 ` qemudev
2023-10-12 16:20 ` qemudev
2023-10-12 16:36 ` checkpatch
2023-10-12 17:39 ` 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=6528ae69.050a0220.fcbfe.9d45SMTPIN_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).