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| pw142807 [PATCH] [v1] net/i40e: updated 24.07 recommended
Date: Fri, 02 Aug 2024 15:17:33 -0700 (PDT)	[thread overview]
Message-ID: <66ad5afd.050a0220.fd457.86c3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801081902.750080-1-hailinx.xu@intel.com>

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

_Performance Testing PASS_

Submitter: hailinx <hailinx.xu@intel.com>
Date: Thursday, August 01 2024 08:19:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b017bdc4c25e2cd6733a9363e9c566b95834cc4

142807 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#172819

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
Fail/Total: 0/2

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

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
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-02 22:17 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801081902.750080-1-hailinx.xu@intel.com>
2024-08-01  8:30 ` |SUCCESS| pw142807 [PATCH v1] net/i40e: updated 24.07 recommended matching list qemudev
2024-08-01  8:34 ` qemudev
2024-08-01  8:58 ` |WARNING| " checkpatch
2024-08-01  9:42 ` |SUCCESS| " 0-day Robot
2024-08-01 18:11 ` |PENDING| pw142807 [PATCH] [v1] net/i40e: updated 24.07 recommended dpdklab
2024-08-01 18:11 ` dpdklab
2024-08-01 18:12 ` dpdklab
2024-08-01 18:12 ` dpdklab
2024-08-01 18:13 ` dpdklab
2024-08-01 18:14 ` |SUCCESS| " dpdklab
2024-08-01 18:15 ` |PENDING| " dpdklab
2024-08-01 18:16 ` dpdklab
2024-08-01 18:17 ` dpdklab
2024-08-01 18:20 ` dpdklab
2024-08-01 18:20 ` dpdklab
2024-08-01 18:21 ` dpdklab
2024-08-01 18:21 ` dpdklab
2024-08-01 18:22 ` dpdklab
2024-08-01 18:25 ` |SUCCESS| " dpdklab
2024-08-01 18:26 ` |PENDING| " dpdklab
2024-08-01 18:27 ` dpdklab
2024-08-01 18:28 ` dpdklab
2024-08-01 18:32 ` dpdklab
2024-08-01 18:36 ` dpdklab
2024-08-01 18:36 ` dpdklab
2024-08-01 18:39 ` dpdklab
2024-08-01 18:41 ` dpdklab
2024-08-01 18:42 ` dpdklab
2024-08-01 18:43 ` dpdklab
2024-08-01 18:44 ` dpdklab
2024-08-01 18:46 ` dpdklab
2024-08-01 18:46 ` dpdklab
2024-08-01 18:47 ` dpdklab
2024-08-01 18:50 ` |SUCCESS| " dpdklab
2024-08-01 18:50 ` |PENDING| " dpdklab
2024-08-01 18:50 ` |SUCCESS| " dpdklab
2024-08-01 18:51 ` |PENDING| " dpdklab
2024-08-01 18:52 ` dpdklab
2024-08-01 18:52 ` dpdklab
2024-08-01 18:56 ` dpdklab
2024-08-01 18:58 ` |SUCCESS| " dpdklab
2024-08-01 20:14 ` |PENDING| " dpdklab
2024-08-01 20:17 ` dpdklab
2024-08-01 20:20 ` dpdklab
2024-08-01 20:24 ` dpdklab
2024-08-01 20:26 ` dpdklab
2024-08-01 20:28 ` dpdklab
2024-08-01 20:33 ` dpdklab
2024-08-01 20:40 ` dpdklab
2024-08-01 20:48 ` dpdklab
2024-08-01 20:55 ` dpdklab
2024-08-01 21:03 ` dpdklab
2024-08-01 21:11 ` dpdklab
2024-08-01 21:17 ` dpdklab
2024-08-01 21:18 ` dpdklab
2024-08-01 21:20 ` dpdklab
2024-08-01 21:25 ` dpdklab
2024-08-01 21:27 ` dpdklab
2024-08-01 21:31 ` dpdklab
2024-08-01 21:33 ` dpdklab
2024-08-01 21:34 ` dpdklab
2024-08-01 21:35 ` dpdklab
2024-08-01 21:39 ` dpdklab
2024-08-01 21:42 ` dpdklab
2024-08-01 21:44 ` dpdklab
2024-08-01 21:44 ` dpdklab
2024-08-01 21:45 ` dpdklab
2024-08-01 21:46 ` dpdklab
2024-08-01 21:46 ` dpdklab
2024-08-01 21:47 ` dpdklab
2024-08-01 21:47 ` dpdklab
2024-08-01 21:52 ` dpdklab
2024-08-01 21:55 ` dpdklab
2024-08-01 21:58 ` dpdklab
2024-08-01 22:09 ` dpdklab
2024-08-01 22:12 ` |SUCCESS| " dpdklab
2024-08-02  0:22 ` dpdklab
2024-08-02 21:29 ` dpdklab
2024-08-02 21:45 ` |PENDING| " dpdklab
2024-08-02 21:53 ` dpdklab
2024-08-02 21:58 ` |SUCCESS| " dpdklab
2024-08-02 22:06 ` dpdklab
2024-08-02 22:07 ` dpdklab
2024-08-02 22:16 ` dpdklab
2024-08-02 22:17 ` dpdklab [this message]
2024-08-02 22:18 ` dpdklab
2024-08-02 22:21 ` dpdklab
2024-08-02 22:25 ` dpdklab
2024-08-02 22:29 ` dpdklab
2024-08-02 22:49 ` dpdklab
2024-08-02 22:50 ` dpdklab
2024-08-03  0:09 ` 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=66ad5afd.050a0220.fd457.86c3SMTPIN_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).