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| pw138487 [PATCH] [v3] dmadev: fix structure alignment
Date: Thu, 21 Mar 2024 15:23:02 -0700 (PDT)	[thread overview]
Message-ID: <65fcb346.170a0220.5d40c.1836SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320072332.1433526-1-wenwux.ma@intel.com>

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

_Performance Testing PASS_

Submitter: Ma, WenwuX <wenwux.ma@intel.com>
Date: Wednesday, March 20 2024 07:23:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138487 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.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           | -2.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.0%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-21 22:31 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320072332.1433526-1-wenwux.ma@intel.com>
2024-03-20  7:14 ` |SUCCESS| pw138487 [PATCH v3] " qemudev
2024-03-20  7:18 ` qemudev
2024-03-20  7:38 ` checkpatch
2024-03-20  8:17 ` |SUCCESS| pw138487 [PATCH] [v3] " dpdklab
2024-03-20  8:23 ` |SUCCESS| pw138487 [PATCH v3] " 0-day Robot
2024-03-20  8:23 ` |SUCCESS| pw138487 [PATCH] [v3] " dpdklab
2024-03-20  8:37 ` dpdklab
2024-03-20  8:37 ` dpdklab
2024-03-20  8:38 ` dpdklab
2024-03-20  8:38 ` dpdklab
2024-03-20  8:39 ` dpdklab
2024-03-20  8:39 ` dpdklab
2024-03-20  8:40 ` dpdklab
2024-03-20  8:40 ` dpdklab
2024-03-20  8:41 ` dpdklab
2024-03-20  8:41 ` dpdklab
2024-03-20  8:42 ` dpdklab
2024-03-20  8:42 ` dpdklab
2024-03-20  8:42 ` dpdklab
2024-03-20  8:43 ` dpdklab
2024-03-20  8:43 ` dpdklab
2024-03-20  8:43 ` dpdklab
2024-03-20  8:44 ` dpdklab
2024-03-20  8:44 ` dpdklab
2024-03-20  8:45 ` dpdklab
2024-03-20  8:45 ` dpdklab
2024-03-20  8:45 ` dpdklab
2024-03-20  8:45 ` dpdklab
2024-03-20  8:46 ` dpdklab
2024-03-20  8:46 ` dpdklab
2024-03-20  8:46 ` dpdklab
2024-03-20  8:46 ` dpdklab
2024-03-20  8:46 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:47 ` dpdklab
2024-03-20  8:48 ` dpdklab
2024-03-20  8:48 ` dpdklab
2024-03-20  8:48 ` dpdklab
2024-03-20  8:48 ` dpdklab
2024-03-20  8:48 ` |FAILURE| " dpdklab
2024-03-20  8:48 ` dpdklab
2024-03-20  8:49 ` dpdklab
2024-03-20  8:49 ` |SUCCESS| " dpdklab
2024-03-20  8:49 ` |FAILURE| " dpdklab
2024-03-20  8:49 ` |SUCCESS| " dpdklab
2024-03-20  8:49 ` |FAILURE| " dpdklab
2024-03-20  8:49 ` |SUCCESS| " dpdklab
2024-03-20  8:50 ` dpdklab
2024-03-20  8:50 ` |FAILURE| " dpdklab
2024-03-20  8:50 ` |SUCCESS| " dpdklab
2024-03-20  8:50 ` |FAILURE| " dpdklab
2024-03-20  8:50 ` |SUCCESS| " dpdklab
2024-03-20  8:50 ` dpdklab
2024-03-20  8:50 ` dpdklab
2024-03-20  8:51 ` |FAILURE| " dpdklab
2024-03-20  8:51 ` dpdklab
2024-03-20  8:51 ` dpdklab
2024-03-20  8:51 ` |SUCCESS| " dpdklab
2024-03-20  8:51 ` dpdklab
2024-03-20  8:51 ` |FAILURE| " dpdklab
2024-03-20  8:52 ` |SUCCESS| " dpdklab
2024-03-20  8:52 ` dpdklab
2024-03-20  8:52 ` dpdklab
2024-03-20  8:52 ` dpdklab
2024-03-20  8:53 ` |FAILURE| " dpdklab
2024-03-20  8:53 ` |SUCCESS| " dpdklab
2024-03-20  8:53 ` dpdklab
2024-03-20  8:53 ` dpdklab
2024-03-20  8:53 ` dpdklab
2024-03-20  8:54 ` dpdklab
2024-03-20  8:54 ` dpdklab
2024-03-20  9:04 ` dpdklab
2024-03-20  9:05 ` |FAILURE| " dpdklab
2024-03-20  9:07 ` |SUCCESS| " dpdklab
2024-03-20 11:30 ` dpdklab
2024-03-21  2:36 ` dpdklab
2024-03-21 22:23 ` dpdklab [this message]
2024-03-21 22:32 ` 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=65fcb346.170a0220.5d40c.1836SMTPIN_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).