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
Subject: |SUCCESS| pw140137 [PATCH] [v1] net/cpfl: check if DPDK is running o
Date: Thu, 16 May 2024 02:27:32 -0700 (PDT)	[thread overview]
Message-ID: <6645d184.050a0220.9522.a4aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240516081243.576723-1-shaiqwani@intel.com>

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

_Performance Testing PASS_

Submitter: Shaiq Wani <shaiqwani@intel.com>
Date: Thursday, May 16 2024 08:12:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:884f83ccf74b5364430d3b21c653d5f6e359e091

140137 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm 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           | 1.0%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.3%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -5.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -3.4%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 0.9%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-16  9:27 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240516081243.576723-1-shaiqwani@intel.com>
2024-05-16  7:52 ` |SUCCESS| pw140137 [PATCH v1] net/cpfl: check if DPDK is running on host IMC ACC qemudev
2024-05-16  7:56 ` qemudev
2024-05-16  8:17 ` checkpatch
2024-05-16  9:04 ` 0-day Robot
2024-05-16  9:27 ` dpdklab [this message]
2024-05-16  9:28 ` |SUCCESS| pw140137 [PATCH] [v1] net/cpfl: check if DPDK is running o dpdklab
2024-05-16  9:29 ` dpdklab
2024-05-16  9:29 ` dpdklab
2024-05-16  9:33 ` dpdklab
2024-05-16  9:46 ` dpdklab
2024-05-16  9:46 ` dpdklab
2024-05-16  9:48 ` dpdklab
2024-05-16  9:49 ` dpdklab
2024-05-16  9:50 ` dpdklab
2024-05-16  9:50 ` dpdklab
2024-05-16  9:50 ` dpdklab
2024-05-16  9:52 ` dpdklab
2024-05-16  9:52 ` dpdklab
2024-05-16  9:53 ` dpdklab
2024-05-16  9:53 ` dpdklab
2024-05-16  9:53 ` dpdklab
2024-05-16  9:54 ` dpdklab
2024-05-16  9:54 ` dpdklab
2024-05-16  9:54 ` dpdklab
2024-05-16  9:54 ` dpdklab
2024-05-16  9:55 ` dpdklab
2024-05-16  9:55 ` dpdklab
2024-05-16  9:55 ` dpdklab
2024-05-16  9:56 ` dpdklab
2024-05-16  9:56 ` dpdklab
2024-05-16  9:56 ` dpdklab
2024-05-16  9:56 ` dpdklab
2024-05-16  9:57 ` dpdklab
2024-05-16  9:57 ` dpdklab
2024-05-16  9:57 ` dpdklab
2024-05-16  9:57 ` dpdklab
2024-05-16  9:58 ` dpdklab
2024-05-16  9:58 ` dpdklab
2024-05-16  9:58 ` dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:01 ` dpdklab
2024-05-16 10:01 ` dpdklab
2024-05-16 10:03 ` dpdklab
2024-05-16 10:03 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:06 ` dpdklab
2024-05-16 10:07 ` dpdklab
2024-05-16 10:09 ` dpdklab
2024-05-16 10:09 ` dpdklab
2024-05-16 10:10 ` dpdklab
2024-05-16 10:10 ` dpdklab
2024-05-16 10:11 ` dpdklab
2024-05-16 10:12 ` dpdklab
2024-05-16 10:13 ` dpdklab
2024-05-16 10:13 ` dpdklab
2024-05-16 10:14 ` dpdklab
2024-05-16 10:14 ` dpdklab
2024-05-16 10:15 ` dpdklab
2024-05-16 10:17 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:21 ` dpdklab
2024-05-16 10:22 ` dpdklab
2024-05-16 10:22 ` dpdklab
2024-05-16 10:23 ` dpdklab
2024-05-16 10:25 ` dpdklab
2024-05-16 10:25 ` dpdklab
2024-05-16 10:35 ` dpdklab
2024-05-16 10:41 ` dpdklab
2024-05-16 10:52 ` dpdklab
2024-05-16 11:02 ` dpdklab
2024-05-16 11:11 ` dpdklab
2024-05-16 12:26 ` 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=6645d184.050a0220.9522.a4aeSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).