automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97157 [PATCH] [v3] ethdev: fix representor port ID search by name
Date: Fri, 20 Aug 2021 17:01:06 -0400 (EDT)	[thread overview]
Message-ID: <20210820210106.A78D830625@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

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

_Performance Testing PASS_

Submitter: Andrew Rybchenko <Andrew.Rybchenko@oktetlabs.ru>
Date: Friday, August 20 2021 12:18:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fdab8f2e17493192d555cd88cf28b06269174326

97157 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

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%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 2           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 2           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-08-20 21:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 21:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-21  0:51 dpdklab
2021-08-21  0:39 dpdklab
2021-08-21  0:27 dpdklab
2021-08-21  0:15 dpdklab
2021-08-21  0:06 dpdklab
2021-08-21  0:02 dpdklab
2021-08-20 23:49 dpdklab
2021-08-20 23:36 dpdklab
2021-08-20 23:23 dpdklab
2021-08-20 23:22 dpdklab
2021-08-20 23:10 dpdklab
2021-08-20 23:01 dpdklab
2021-08-20 22:50 dpdklab
2021-08-20 22:29 dpdklab
2021-08-20 22:27 dpdklab
2021-08-20 21:40 dpdklab
2021-08-20 21:21 dpdklab
2021-08-20 21:19 dpdklab
2021-08-20 21:14 dpdklab
2021-08-20 21:13 dpdklab
2021-08-20 20:55 dpdklab
2021-08-20 20:55 dpdklab
2021-08-20 20:49 dpdklab
2021-08-20 20:47 dpdklab
2021-08-20 20:46 dpdklab
2021-08-20 20:34 dpdklab
2021-08-20 20:27 dpdklab
2021-08-20 20:26 dpdklab
2021-08-20 20:26 dpdklab
2021-08-20 20:25 dpdklab
2021-08-20 20:17 dpdklab
2021-08-20 20:11 dpdklab
2021-08-20 20:06 dpdklab
2021-08-20 19:59 dpdklab
2021-08-20 19:47 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=20210820210106.A78D830625@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --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).