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| pw136232 [PATCH] maintainers: update for fm10k/ifc drivers
Date: Wed, 31 Jan 2024 06:15:23 -0800 (PST)	[thread overview]
Message-ID: <65ba55fb.630a0220.1c6aa.d142SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Xiao Wang <xiao.w.wang@intel.com>
Date: Wednesday, January 31 2024 09:50:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5eedf66ac0e5ce62cd333e523996c63a3c4c2c00

136232 --> performance testing pass

Test environment and result as below:

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-31 14:15 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 14:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31 15:41 dpdklab
2024-01-31 15:17 dpdklab
2024-01-31 15:07 dpdklab
2024-01-31 15:00 dpdklab
2024-01-31 15:00 dpdklab
2024-01-31 14:57 dpdklab
2024-01-31 14:54 dpdklab
2024-01-31 14:53 dpdklab
2024-01-31 14:51 dpdklab
2024-01-31 14:49 dpdklab
2024-01-31 14:48 dpdklab
2024-01-31 14:47 dpdklab
2024-01-31 14:46 dpdklab
2024-01-31 14:46 dpdklab
2024-01-31 14:43 dpdklab
2024-01-31 14:43 dpdklab
2024-01-31 14:42 dpdklab
2024-01-31 14:41 dpdklab
2024-01-31 14:40 dpdklab
2024-01-31 14:39 dpdklab
2024-01-31 14:38 dpdklab
2024-01-31 14:37 dpdklab
2024-01-31 14:36 dpdklab
2024-01-31 14:35 dpdklab
2024-01-31 14:34 dpdklab
2024-01-31 14:34 dpdklab
2024-01-31 14:33 dpdklab
2024-01-31 14:33 dpdklab
2024-01-31 14:32 dpdklab
2024-01-31 14:32 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:26 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:21 dpdklab
2024-01-31 14:21 dpdklab
2024-01-31 14:20 dpdklab
2024-01-31 14:20 dpdklab
2024-01-31 14:19 dpdklab
2024-01-31 14:18 dpdklab
2024-01-31 14:17 dpdklab
2024-01-31 14:17 dpdklab
2024-01-31 14:16 dpdklab
2024-01-31 14:15 dpdklab
2024-01-31 14:14 dpdklab
2024-01-31 14:14 dpdklab
2024-01-31 14:13 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:10 dpdklab
2024-01-31 14:10 dpdklab
2024-01-31 14:10 dpdklab
     [not found] <20240131095008.1547927-1-xiao.w.wang@intel.com>
2024-01-31  9:45 ` qemudev
2024-01-31  9:49 ` qemudev
2024-01-31  9:51 ` checkpatch
2024-01-31 10:43 ` 0-day Robot

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=65ba55fb.630a0220.1c6aa.d142SMTPIN_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).