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: |SUCCESS| pw104570 [PATCH] net/mlx4: fix empty ETH spec with VLAN support
Date: Mon, 22 Nov 2021 15:37:15 +0000 (UTC)	[thread overview]
Message-ID: <20211122153715.3DEFB6056E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Xiaoyu Min <jackmin@nvidia.com>
Date: Monday, November 22 2021 13:53:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0c6e27549c03695f85d949f5195a166b449b419c

104570 --> 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: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 0.2%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-11-22 15:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 15:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22 16:32 dpdklab
2021-11-22 16:21 dpdklab
2021-11-22 16:15 dpdklab
2021-11-22 16:06 dpdklab
2021-11-22 16:06 dpdklab
2021-11-22 16:03 dpdklab
2021-11-22 15:54 dpdklab
2021-11-22 15:49 dpdklab
2021-11-22 15:46 dpdklab
2021-11-22 15:36 dpdklab
2021-11-22 15:36 dpdklab
2021-11-22 15:32 dpdklab
2021-11-22 15:29 dpdklab
2021-11-22 15:24 dpdklab
2021-11-22 15:23 dpdklab
2021-11-22 15:16 dpdklab
2021-11-22 15:11 dpdklab
2021-11-22 15:07 dpdklab
2021-11-22 15:06 dpdklab
2021-11-22 15:01 dpdklab
2021-11-22 14:46 dpdklab
     [not found] <3672e46dd1181429c73952a93cc211ad11769b99.1637589050.git.jackmin@nvidia.com>
2021-11-22 13:54 ` checkpatch
2021-11-22 14:18 ` 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=20211122153715.3DEFB6056E@dpdk-ubuntu.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).