From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org
Subject: |SUCCESS| pw105812 [PATCH] common/mlx5: fix MR lookup for non-contiguous mempool
Date: Fri, 14 Jan 2022 17:50:32 +0000 (UTC) [thread overview]
Message-ID: <20220114175032.089D0602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/105812
_Performance Testing PASS_
Submitter: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Date: Friday, January 14 2022 10:52:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f716880ee53ac1e50c9c75dc749886e3257bb8f
105812 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20666/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-01-14 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 17:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-14 21:44 dpdklab
2022-01-14 20:33 dpdklab
2022-01-14 20:26 dpdklab
2022-01-14 19:43 dpdklab
2022-01-14 19:31 dpdklab
2022-01-14 19:28 dpdklab
2022-01-14 19:15 dpdklab
2022-01-14 18:13 dpdklab
2022-01-14 18:11 dpdklab
2022-01-14 18:07 dpdklab
2022-01-14 18:00 dpdklab
2022-01-14 17:59 dpdklab
2022-01-14 17:54 dpdklab
[not found] <20220114105217.343139-1-dkozlyuk@nvidia.com>
2022-01-14 10:53 ` checkpatch
2022-01-14 12: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=20220114175032.089D0602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=dpdk-test-reports@dpdk.org \
--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).