automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw134955 [PATCH] lib/dmadev: get DMA device using device I
Date: Fri, 08 Dec 2023 03:04:52 -0800 (PST)	[thread overview]
Message-ID: <6572f854.050a0220.e8c7c.5ad8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/134955

_Performance Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Friday, December 08 2023 07:55:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

134955 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-78-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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-78-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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28565/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-12-08 11:04 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 11:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-09  0:16 dpdklab
2023-12-08 13:47 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:57 dpdklab
2023-12-08 11:57 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:51 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:45 dpdklab
2023-12-08 11:45 dpdklab
2023-12-08 11:45 dpdklab
2023-12-08 11:44 dpdklab
2023-12-08 11:43 dpdklab
2023-12-08 11:43 dpdklab
2023-12-08 11:42 dpdklab
2023-12-08 11:39 dpdklab
2023-12-08 11:38 dpdklab
2023-12-08 11:38 dpdklab
2023-12-08 11:37 dpdklab
2023-12-08 11:37 dpdklab
2023-12-08 11:36 dpdklab
2023-12-08 11:36 dpdklab
2023-12-08 11:36 dpdklab
2023-12-08 11:35 dpdklab
2023-12-08 11:27 dpdklab
2023-12-08 11:23 dpdklab
2023-12-08 11:23 dpdklab
2023-12-08 11:21 dpdklab
2023-12-08 11:19 dpdklab
2023-12-08 11:18 dpdklab
2023-12-08 11:17 dpdklab
2023-12-08 11:17 dpdklab
2023-12-08 11:08 dpdklab
2023-12-08 11:07 dpdklab
2023-12-08 11:05 dpdklab
2023-12-08 11:05 dpdklab
2023-12-08 11:04 dpdklab
2023-12-08 10:55 dpdklab
2023-12-08 10:54 dpdklab
2023-12-08 10:48 dpdklab
2023-12-08 10:35 dpdklab
2023-12-08 10:30 dpdklab
2023-12-08 10:25 dpdklab
2023-12-08 10:14 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=6572f854.050a0220.e8c7c.5ad8SMTPIN_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).