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| pw136016 [PATCH] [v4,1/1] ethdev: parsing multiple represe
Date: Sun, 21 Jan 2024 12:04:49 -0800 (PST)	[thread overview]
Message-ID: <65ad78e1.050a0220.e0668.5787SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Harman Kalra <hkalra@marvell.com>
Date: Sunday, January 21 2024 19:19:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39a8b1251b204d3898b4c462184f60bda1b64698

136016 --> 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.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-21 20:04 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21 20:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 23:22 dpdklab
2024-01-22 23:14 dpdklab
2024-01-21 21:22 dpdklab
2024-01-21 21:10 dpdklab
2024-01-21 21:08 dpdklab
2024-01-21 21:08 dpdklab
2024-01-21 21:06 dpdklab
2024-01-21 21:04 dpdklab
2024-01-21 20:56 dpdklab
2024-01-21 20:54 dpdklab
2024-01-21 20:53 dpdklab
2024-01-21 20:52 dpdklab
2024-01-21 20:51 dpdklab
2024-01-21 20:48 dpdklab
2024-01-21 20:43 dpdklab
2024-01-21 20:41 dpdklab
2024-01-21 20:41 dpdklab
2024-01-21 20:41 dpdklab
2024-01-21 20:40 dpdklab
2024-01-21 20:39 dpdklab
2024-01-21 20:37 dpdklab
2024-01-21 20:35 dpdklab
2024-01-21 20:35 dpdklab
2024-01-21 20:35 dpdklab
2024-01-21 20:35 dpdklab
2024-01-21 20:34 dpdklab
2024-01-21 20:34 dpdklab
2024-01-21 20:33 dpdklab
2024-01-21 20:33 dpdklab
2024-01-21 20:31 dpdklab
2024-01-21 20:30 dpdklab
2024-01-21 20:29 dpdklab
2024-01-21 20:29 dpdklab
2024-01-21 20:28 dpdklab
2024-01-21 20:27 dpdklab
2024-01-21 20:26 dpdklab
2024-01-21 20:25 dpdklab
2024-01-21 20:24 dpdklab
2024-01-21 20:24 dpdklab
2024-01-21 20:23 dpdklab
2024-01-21 20:23 dpdklab
2024-01-21 20:23 dpdklab
2024-01-21 20:20 dpdklab
2024-01-21 20:19 dpdklab
2024-01-21 20:19 dpdklab
2024-01-21 20:19 dpdklab
2024-01-21 20:16 dpdklab
2024-01-21 20:15 dpdklab
2024-01-21 20:12 dpdklab
2024-01-21 20:12 dpdklab
2024-01-21 20:11 dpdklab
2024-01-21 20:10 dpdklab
2024-01-21 20:10 dpdklab
2024-01-21 20:10 dpdklab
2024-01-21 20:08 dpdklab
2024-01-21 20:08 dpdklab
2024-01-21 20:08 dpdklab
2024-01-21 20:07 dpdklab
2024-01-21 20:06 dpdklab
2024-01-21 20:06 dpdklab
2024-01-21 20:06 dpdklab
2024-01-21 20:05 dpdklab
2024-01-21 20:05 dpdklab
2024-01-21 20:05 dpdklab
2024-01-21 20:05 dpdklab
2024-01-21 20:04 dpdklab
2024-01-21 20:03 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=65ad78e1.050a0220.e0668.5787SMTPIN_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).