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| pw139435 [PATCH] usertools/devbind: add ODM DMA device
Date: Wed, 17 Apr 2024 04:04:53 -0700 (PDT) [thread overview]
Message-ID: <661facd5.d40a0220.a4d58.715eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417071109.104-1-anoobj@marvell.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/139435
_Performance Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, April 17 2024 07:11:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139435 --> 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-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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29800/
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-04-17 11:04 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417071109.104-1-anoobj@marvell.com>
2024-04-17 6:53 ` qemudev
2024-04-17 6:57 ` qemudev
2024-04-17 7:12 ` checkpatch
2024-04-17 8:04 ` 0-day Robot
2024-04-17 10:52 ` dpdklab
2024-04-17 10:53 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:04 ` dpdklab [this message]
2024-04-17 11:05 ` dpdklab
2024-04-17 11:07 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:09 ` dpdklab
2024-04-17 11:09 ` dpdklab
2024-04-17 11:10 ` dpdklab
2024-04-17 11:10 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:46 ` dpdklab
2024-04-17 11:46 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:51 ` dpdklab
2024-04-17 11:51 ` dpdklab
2024-04-17 11:53 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 11:57 ` dpdklab
2024-04-17 11:58 ` dpdklab
2024-04-17 11:58 ` dpdklab
2024-04-17 11:59 ` dpdklab
2024-04-17 12:02 ` dpdklab
2024-04-17 12:02 ` dpdklab
2024-04-17 12:03 ` dpdklab
2024-04-17 12:03 ` dpdklab
2024-04-17 12:05 ` dpdklab
2024-04-17 12:05 ` dpdklab
2024-04-17 12:06 ` dpdklab
2024-04-17 12:07 ` dpdklab
2024-04-17 12:07 ` dpdklab
2024-04-17 12:08 ` dpdklab
2024-04-17 12:08 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:12 ` dpdklab
2024-04-17 12:14 ` dpdklab
2024-04-17 12:14 ` dpdklab
2024-04-17 12:15 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:18 ` dpdklab
2024-04-17 12:18 ` dpdklab
2024-04-17 12:19 ` dpdklab
2024-04-17 12:19 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:22 ` dpdklab
2024-04-17 12:22 ` dpdklab
2024-04-17 12:27 ` dpdklab
2024-04-17 12:30 ` dpdklab
2024-04-17 12:30 ` dpdklab
2024-04-17 12:31 ` dpdklab
2024-04-17 12:33 ` dpdklab
2024-04-17 12:33 ` dpdklab
2024-04-17 12:34 ` dpdklab
2024-04-17 12:36 ` dpdklab
2024-04-17 12:39 ` dpdklab
2024-04-17 12:41 ` dpdklab
2024-04-17 12:44 ` dpdklab
2024-04-17 12:49 ` dpdklab
2024-04-17 13:04 ` dpdklab
2024-04-17 13:08 ` dpdklab
2024-04-17 13:10 ` dpdklab
2024-04-17 13:12 ` dpdklab
2024-04-17 13:12 ` dpdklab
2024-04-17 14:29 ` dpdklab
2024-04-17 14:59 ` 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=661facd5.d40a0220.a4d58.715eSMTPIN_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).