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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125230 [PATCH] [v5] testpmd: go back to using cmdline_interact
Date: Fri, 17 Mar 2023 18:37:30 +0000 (UTC)	[thread overview]
Message-ID: <20230317183730.C5B0E6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 17 2023 16:59:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ce5440e0350df101443aa4d0e96bea0a06ef9364

125230 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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           | -2.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.7%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-17 18:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 18:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  2:12 dpdklab
2023-03-21 23:53 dpdklab
2023-03-21 16:25 dpdklab
2023-03-20  2:24 dpdklab
2023-03-20  1:38 dpdklab
2023-03-19 13:15 dpdklab
2023-03-19 13:10 dpdklab
2023-03-17 20:51 dpdklab
2023-03-17 19:28 dpdklab
2023-03-17 19:24 dpdklab
2023-03-17 19:16 dpdklab
2023-03-17 19:16 dpdklab
2023-03-17 18:58 dpdklab
2023-03-17 18:48 dpdklab
2023-03-17 18:44 dpdklab
2023-03-17 18:43 dpdklab
2023-03-17 18:43 dpdklab
2023-03-17 18:39 dpdklab
2023-03-17 18:37 dpdklab
2023-03-17 18:31 dpdklab
2023-03-17 18:31 dpdklab
2023-03-17 18:28 dpdklab
2023-03-17 18:24 dpdklab
2023-03-17 18:23 dpdklab
2023-03-17 18:22 dpdklab
2023-03-17 18:20 dpdklab
2023-03-17 18:19 dpdklab
2023-03-17 18:15 dpdklab
2023-03-17 18:14 dpdklab
2023-03-17 18:11 dpdklab
2023-03-17 18:08 dpdklab
2023-03-17 18:08 dpdklab
2023-03-17 18:04 dpdklab
2023-03-17 18:01 dpdklab
     [not found] <20230317165941.62619-1-stephen@networkplumber.org>
2023-03-17 16:52 ` |SUCCESS| pw125230 [PATCH v5] " qemudev
2023-03-17 16:56 ` qemudev
2023-03-17 17:00 ` checkpatch
2023-03-17 19:39 ` 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=20230317183730.C5B0E6011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).