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| pw137511-137513 [PATCH] [3/3] net/tap: compute TC handle c
Date: Fri, 01 Mar 2024 03:42:09 -0800 (PST)	[thread overview]
Message-ID: <65e1bf11.170a0220.c6f94.6a03SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229173154.121491-4-stephen@networkplumber.org>

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, February 29 2024 17:31:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f60df26faa3c90fc66d356e16347acd046971441

137511-137513 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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           | 2.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.5%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-01 11:42 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229173154.121491-4-stephen@networkplumber.org>
2024-02-29 17:09 ` |SUCCESS| pw137511-137513 [PATCH 3/3] net/tap: compute TC handle correctly qemudev
2024-02-29 17:14 ` qemudev
2024-02-29 17:33 ` |WARNING| pw137513 " checkpatch
2024-02-29 20:21 ` |SUCCESS| pw137511-137513 [PATCH] [3/3] net/tap: compute TC handle c dpdklab
2024-02-29 20:34 ` dpdklab
2024-02-29 20:37 ` dpdklab
2024-02-29 20:44 ` dpdklab
2024-02-29 20:44 ` |SUCCESS| pw137513 [PATCH 3/3] net/tap: compute TC handle correctly 0-day Robot
2024-02-29 20:49 ` |SUCCESS| pw137511-137513 [PATCH] [3/3] net/tap: compute TC handle c dpdklab
2024-02-29 20:51 ` dpdklab
2024-02-29 20:55 ` dpdklab
2024-02-29 20:56 ` dpdklab
2024-02-29 20:56 ` dpdklab
2024-02-29 21:04 ` dpdklab
2024-02-29 21:05 ` dpdklab
2024-02-29 21:05 ` dpdklab
2024-02-29 21:07 ` dpdklab
2024-02-29 21:07 ` dpdklab
2024-02-29 21:13 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 22:19 ` dpdklab
2024-03-01  0:39 ` dpdklab
2024-03-01  0:40 ` dpdklab
2024-03-01  0:40 ` dpdklab
2024-03-01  0:40 ` dpdklab
2024-03-01  0:45 ` dpdklab
2024-03-01  0:46 ` dpdklab
2024-03-01  0:46 ` dpdklab
2024-03-01  0:47 ` dpdklab
2024-03-01  0:48 ` dpdklab
2024-03-01  0:48 ` dpdklab
2024-03-01  0:48 ` dpdklab
2024-03-01  0:48 ` dpdklab
2024-03-01  0:48 ` dpdklab
2024-03-01  0:49 ` dpdklab
2024-03-01  0:49 ` dpdklab
2024-03-01  0:50 ` dpdklab
2024-03-01  0:57 ` dpdklab
2024-03-01  0:57 ` dpdklab
2024-03-01  0:57 ` dpdklab
2024-03-01  0:58 ` dpdklab
2024-03-01  0:58 ` dpdklab
2024-03-01  0:58 ` dpdklab
2024-03-01  0:58 ` dpdklab
2024-03-01  0:59 ` dpdklab
2024-03-01  0:59 ` dpdklab
2024-03-01  1:00 ` dpdklab
2024-03-01  1:00 ` dpdklab
2024-03-01  1:01 ` dpdklab
2024-03-01  1:01 ` dpdklab
2024-03-01  1:03 ` dpdklab
2024-03-01  1:03 ` dpdklab
2024-03-01  1:04 ` dpdklab
2024-03-01  1:05 ` dpdklab
2024-03-01  1:06 ` dpdklab
2024-03-01  1:06 ` dpdklab
2024-03-01  1:06 ` dpdklab
2024-03-01  1:08 ` dpdklab
2024-03-01  1:22 ` dpdklab
2024-03-01  1:31 ` dpdklab
2024-03-01  1:31 ` dpdklab
2024-03-01  1:32 ` dpdklab
2024-03-01  1:33 ` dpdklab
2024-03-01  1:43 ` dpdklab
2024-03-01  1:59 ` dpdklab
2024-03-01  2:00 ` dpdklab
2024-03-01  2:08 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  7:41 ` dpdklab
2024-03-01 11:03 ` dpdklab
2024-03-01 11:08 ` dpdklab
2024-03-01 11:12 ` dpdklab
2024-03-01 11:42 ` dpdklab [this message]
2024-03-02 11:35 ` dpdklab
2024-03-03 21:00 ` dpdklab
2024-03-03 21:39 ` dpdklab
2024-03-03 22:06 ` 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=65e1bf11.170a0220.c6f94.6a03SMTPIN_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).