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| pw128463 [PATCH] net/cnxk: support port ID flow action ite
Date: Fri, 09 Jun 2023 16:11:19 -0700 (PDT)	[thread overview]
Message-ID: <6483b197.b00a0220.576be.16dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Friday, June 09 2023 11:18:01 
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: master
  CommitID:acd91653e50b4cfaa9c0bd1e68b48d7c1cacd93f

128463 --> 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.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-09 23:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 23:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-11  6:21 dpdklab
2023-06-09 23:20 dpdklab
2023-06-09 23:15 dpdklab
2023-06-09 23:07 dpdklab
2023-06-09 23:06 dpdklab
2023-06-09 18:22 dpdklab
2023-06-09 18:21 dpdklab
2023-06-09 15:56 dpdklab
2023-06-09 14:40 dpdklab
2023-06-09 13:54 dpdklab
2023-06-09 13:50 dpdklab
2023-06-09 13:49 dpdklab
2023-06-09 13:47 dpdklab
2023-06-09 13:43 dpdklab
2023-06-09 13:38 dpdklab
2023-06-09 13:31 dpdklab
2023-06-09 13:30 dpdklab
2023-06-09 13:29 dpdklab
2023-06-09 13:28 dpdklab
2023-06-09 13:22 dpdklab
2023-06-09 12:48 dpdklab
2023-06-09 12:35 dpdklab
2023-06-09 12:31 dpdklab
2023-06-09 12:27 dpdklab
2023-06-09 12:22 dpdklab
2023-06-09 12:21 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=6483b197.b00a0220.576be.16dfSMTPIN_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).