automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125227 [PATCH] doc: deprecation notice to remove net/bnx2x driver
Date: Fri, 17 Mar 2023 13:58:06 +0000 (UTC)	[thread overview]
Message-ID: <20230317135806.AA6BD6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125227

_Performance Testing PASS_

Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Friday, March 17 2023 12:30:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823

125227 --> performance testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 128     | 64         | 0.0%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 512     | 64         | -0.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 128     | 64         | -0.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -0.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-17 13:58 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 13:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-20 13:17 dpdklab
2023-03-20 13:17 dpdklab
2023-03-20 13:13 dpdklab
2023-03-20 13:09 dpdklab
2023-03-20 13:04 dpdklab
2023-03-20 13:03 dpdklab
2023-03-20 12:56 dpdklab
2023-03-20 12:50 dpdklab
2023-03-20 12:48 dpdklab
2023-03-20 12:44 dpdklab
2023-03-20 12:39 dpdklab
2023-03-20 12:34 dpdklab
2023-03-20 12:32 dpdklab
2023-03-20 10:47 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:20 dpdklab
2023-03-20 10:12 dpdklab
2023-03-20 10:04 dpdklab
2023-03-20 10:03 dpdklab
2023-03-20 10:01 dpdklab
2023-03-20  9:52 dpdklab
2023-03-20  9:50 dpdklab
2023-03-20  9:46 dpdklab
2023-03-20  9:38 dpdklab
2023-03-20  8:24 dpdklab
2023-03-19 20:14 dpdklab
2023-03-19 19:26 dpdklab
2023-03-19 10:52 dpdklab
2023-03-19 10:51 dpdklab
2023-03-17 15:05 dpdklab
2023-03-17 15:02 dpdklab
2023-03-17 14:59 dpdklab
2023-03-17 14:10 dpdklab
2023-03-17 14:09 dpdklab
2023-03-17 14:02 dpdklab
2023-03-17 13:57 dpdklab
2023-03-17 13:54 dpdklab
2023-03-17 13:53 dpdklab
2023-03-17 13:48 dpdklab
2023-03-17 13:45 dpdklab
2023-03-17 13:44 dpdklab
2023-03-17 13:37 dpdklab
2023-03-17 13:34 dpdklab
2023-03-17 13:34 dpdklab
2023-03-17 13:33 dpdklab
2023-03-17 13:33 dpdklab
2023-03-17 13:28 dpdklab
2023-03-17 13:28 dpdklab
2023-03-17 13:22 dpdklab
2023-03-17 13:20 dpdklab
2023-03-17 13:19 dpdklab
2023-03-17 13:18 dpdklab
2023-03-17 13:12 dpdklab
2023-03-17 13:06 dpdklab
     [not found] <20230317123011.3146170-1-jerinj@marvell.com>
2023-03-17 12:20 ` qemudev
2023-03-17 12:24 ` qemudev
2023-03-17 12:31 ` checkpatch

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=20230317135806.AA6BD6011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).