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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw132608 [PATCH] [v2] ethdev: clarify device queue state a
Date: Fri, 13 Oct 2023 09:32:31 -0700 (PDT)	[thread overview]
Message-ID: <6529711f.0c0a0220.67cde.42a3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/132608

_Performance Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Friday, October 13 2023 15:57:23 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:64b86ec39b328c4a3f7305e233a9399092c0a419

132608 --> 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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 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.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-13 16:32 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 16:32 dpdklab [this message]
2023-10-13 16:32 dpdklab
2023-10-13 16:32 dpdklab
2023-10-13 16:34 dpdklab
2023-10-13 16:34 dpdklab
2023-10-13 16:35 dpdklab
2023-10-13 16:35 dpdklab
2023-10-13 16:35 dpdklab
2023-10-13 16:36 dpdklab
2023-10-13 16:36 dpdklab
2023-10-13 16:36 dpdklab
2023-10-13 16:36 dpdklab
2023-10-13 16:37 dpdklab
2023-10-13 16:38 dpdklab
2023-10-13 16:39 dpdklab
2023-10-13 16:42 dpdklab
2023-10-13 16:43 dpdklab
2023-10-13 16:43 dpdklab
2023-10-13 16:44 dpdklab
2023-10-13 16:45 dpdklab
2023-10-13 16:45 dpdklab
2023-10-13 16:46 dpdklab
2023-10-13 16:48 dpdklab
2023-10-13 16:48 dpdklab
2023-10-13 16:48 dpdklab
2023-10-13 16:50 dpdklab
2023-10-13 16:57 dpdklab
2023-10-13 16:58 dpdklab
2023-10-13 16:59 dpdklab
2023-10-13 17:00 dpdklab
2023-10-13 17:01 dpdklab
2023-10-13 17:03 dpdklab
2023-10-13 17:04 dpdklab
2023-10-13 17:11 dpdklab
2023-10-13 17:12 dpdklab
2023-10-13 17:12 dpdklab
2023-10-13 17:15 dpdklab
2023-10-13 17:16 dpdklab
2023-10-13 17:17 dpdklab
2023-10-13 17:19 dpdklab
2023-10-13 17:22 dpdklab
2023-10-13 17:25 dpdklab
2023-10-13 17:28 dpdklab
2023-10-13 17:28 dpdklab
2023-10-13 17:29 dpdklab
2023-10-13 17:33 dpdklab
2023-10-13 17:35 dpdklab
2023-10-13 17:53 dpdklab
2023-10-13 18:12 dpdklab
2023-10-13 18:15 dpdklab
2023-10-13 18:21 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=6529711f.0c0a0220.67cde.42a3SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).