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| pw138849 [PATCH] [v1] net/ice: updated 24.03 recommended m
Date: Mon, 01 Apr 2024 22:40:20 -0700 (PDT)	[thread overview]
Message-ID: <660b9a44.050a0220.176e2.e3d5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240327050729.459392-1-hailinx.xu@intel.com>

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

_Performance Testing PASS_

Submitter: hailinx <hailinx.xu@intel.com>
Date: Wednesday, March 27 2024 05:07:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2c54ea7a59dfc0a819d3527309c62846fc8853af

138849 --> performance testing pass

Test environment and result as below:

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.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.9%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-02  5:40 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327050729.459392-1-hailinx.xu@intel.com>
2024-03-27  5:17 ` |SUCCESS| pw138849 [PATCH v1] net/ice: updated 24.03 recommended matching list qemudev
2024-03-27  5:21 ` qemudev
2024-03-27  5:41 ` |WARNING| " checkpatch
2024-03-27  6:45 ` |SUCCESS| " 0-day Robot
2024-03-27  6:58 ` |SUCCESS| pw138849 [PATCH] [v1] net/ice: updated 24.03 recommended m dpdklab
2024-03-27  6:59 ` dpdklab
2024-03-27  7:00 ` dpdklab
2024-03-27  7:00 ` dpdklab
2024-03-27  7:01 ` dpdklab
2024-03-27  7:01 ` dpdklab
2024-03-27  7:02 ` dpdklab
2024-03-27  7:02 ` dpdklab
2024-03-27  7:02 ` dpdklab
2024-03-27  7:03 ` dpdklab
2024-03-27  7:07 ` dpdklab
2024-03-27  7:07 ` dpdklab
2024-03-27  7:08 ` dpdklab
2024-03-27  7:08 ` dpdklab
2024-03-27  7:09 ` dpdklab
2024-03-27  7:09 ` dpdklab
2024-03-27  7:10 ` dpdklab
2024-03-27  7:10 ` dpdklab
2024-03-27  7:11 ` dpdklab
2024-03-27  7:11 ` dpdklab
2024-03-27  7:12 ` dpdklab
2024-03-27  7:12 ` dpdklab
2024-03-27  7:12 ` dpdklab
2024-03-27  7:12 ` dpdklab
2024-03-27  7:14 ` dpdklab
2024-03-27  7:16 ` dpdklab
2024-03-27  7:16 ` dpdklab
2024-03-27  7:20 ` dpdklab
2024-03-27  7:31 ` dpdklab
2024-03-27  7:31 ` dpdklab
2024-03-27  7:32 ` dpdklab
2024-03-27  7:33 ` dpdklab
2024-03-27  7:33 ` dpdklab
2024-03-27  7:34 ` dpdklab
2024-03-27  7:34 ` dpdklab
2024-03-27  7:35 ` dpdklab
2024-03-27  7:35 ` dpdklab
2024-03-27  7:35 ` dpdklab
2024-03-27  7:36 ` dpdklab
2024-03-27  7:36 ` dpdklab
2024-03-27  7:36 ` dpdklab
2024-03-27  7:36 ` dpdklab
2024-03-27  7:37 ` dpdklab
2024-03-27  7:46 ` dpdklab
2024-03-27  7:51 ` dpdklab
2024-03-27  7:51 ` dpdklab
2024-03-27  7:52 ` dpdklab
2024-03-27  7:53 ` dpdklab
2024-03-27  7:53 ` dpdklab
2024-03-27  7:54 ` dpdklab
2024-03-27  7:55 ` dpdklab
2024-03-27  7:55 ` dpdklab
2024-03-27  7:56 ` dpdklab
2024-03-27  7:56 ` dpdklab
2024-03-27  7:57 ` dpdklab
2024-03-27  7:57 ` dpdklab
2024-03-27  7:58 ` dpdklab
2024-03-27  8:02 ` dpdklab
2024-03-27  8:12 ` dpdklab
2024-03-27  8:28 ` dpdklab
2024-03-27  8:33 ` dpdklab
2024-03-27  8:33 ` dpdklab
2024-03-27  8:34 ` dpdklab
2024-03-27  8:34 ` dpdklab
2024-03-27  8:36 ` dpdklab
2024-03-27  8:37 ` dpdklab
2024-03-27  8:40 ` dpdklab
2024-03-27  8:42 ` dpdklab
2024-03-27  8:44 ` dpdklab
2024-03-27  8:45 ` dpdklab
2024-03-27  8:45 ` dpdklab
2024-03-27  8:47 ` dpdklab
2024-03-27  8:51 ` dpdklab
2024-03-27  8:52 ` dpdklab
2024-03-27  8:53 ` dpdklab
2024-03-27  8:57 ` dpdklab
2024-03-27  8:58 ` dpdklab
2024-03-27  9:00 ` dpdklab
2024-03-27  9:01 ` dpdklab
2024-03-27  9:05 ` dpdklab
2024-03-27  9:14 ` dpdklab
2024-03-27  9:35 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-04-02  5:40 ` dpdklab [this message]
2024-04-02  5:44 ` dpdklab
2024-04-02  5:47 ` dpdklab
2024-04-02  5:52 ` dpdklab
2024-04-02  6:11 ` 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=660b9a44.050a0220.176e2.e3d5SMTPIN_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).