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| pw130093 [PATCH] [1/1] net/sfc: add missing error code ind
Date: Thu, 10 Aug 2023 13:46:10 -0700 (PDT)	[thread overview]
Message-ID: <64d54c92.170a0220.6ab94.0409SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Thursday, August 10 2023 17:36:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130093 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-10 20:46 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 20:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  3:47 dpdklab
2023-08-14  3:38 dpdklab
2023-08-14  3:35 dpdklab
2023-08-14  3:35 dpdklab
2023-08-14  3:34 dpdklab
2023-08-14  3:34 dpdklab
2023-08-14  3:33 dpdklab
2023-08-14  3:32 dpdklab
2023-08-14  3:32 dpdklab
2023-08-14  3:32 dpdklab
2023-08-14  3:31 dpdklab
2023-08-14  0:14 dpdklab
2023-08-13 19:32 dpdklab
2023-08-11 20:00 dpdklab
2023-08-11 19:19 dpdklab
2023-08-11 19:09 dpdklab
2023-08-11 18:54 dpdklab
2023-08-11 18:43 dpdklab
2023-08-11 14:58 dpdklab
2023-08-11  6:59 dpdklab
2023-08-11  0:41 dpdklab
2023-08-11  0:40 dpdklab
2023-08-11  0:40 dpdklab
2023-08-11  0:39 dpdklab
2023-08-11  0:37 dpdklab
2023-08-11  0:37 dpdklab
2023-08-11  0:36 dpdklab
2023-08-11  0:30 dpdklab
2023-08-11  0:29 dpdklab
2023-08-11  0:29 dpdklab
2023-08-11  0:11 dpdklab
2023-08-11  0:05 dpdklab
2023-08-11  0:01 dpdklab
2023-08-10 23:50 dpdklab
2023-08-10 23:42 dpdklab
2023-08-10 23:32 dpdklab
2023-08-10 23:32 dpdklab
2023-08-10 23:30 dpdklab
2023-08-10 23:22 dpdklab
2023-08-10 23:22 dpdklab
2023-08-10 23:20 dpdklab
2023-08-10 23:20 dpdklab
2023-08-10 23:19 dpdklab
2023-08-10 23:18 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:13 dpdklab
2023-08-10 23:13 dpdklab
2023-08-10 23:12 dpdklab
2023-08-10 23:12 dpdklab
2023-08-10 23:12 dpdklab
2023-08-10 23:11 dpdklab
2023-08-10 23:11 dpdklab
2023-08-10 23:11 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 22:29 dpdklab
2023-08-10 22:14 dpdklab
2023-08-10 21:08 dpdklab
2023-08-10 20:54 dpdklab
2023-08-10 20:44 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=64d54c92.170a0220.6ab94.0409SMTPIN_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).