From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137501 [PATCH] [v2] net/mlx5: add HWS support for matchi
Date: Sun, 03 Mar 2024 03:14:54 -0800 (PST) [thread overview]
Message-ID: <65e45bae.170a0220.3ec81.028fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229134913.3197558-1-michaelba@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137501
_Performance Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Thursday, February 29 2024 13:49:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:387aefe9fab8f1033071659a758ccda61a220ffd
137501 --> 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 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -2.6% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29339/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-03 11:14 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229134913.3197558-1-michaelba@nvidia.com>
2024-02-29 13:34 ` |SUCCESS| pw137501 [PATCH v2] net/mlx5: add HWS support for matching ingress metadata qemudev
2024-02-29 13:38 ` qemudev
2024-02-29 13:50 ` checkpatch
2024-02-29 18:13 ` |SUCCESS| pw137501 [PATCH] [v2] net/mlx5: add HWS support for matchi dpdklab
2024-02-29 18:15 ` dpdklab
2024-02-29 18:20 ` dpdklab
2024-02-29 18:25 ` dpdklab
2024-02-29 18:32 ` dpdklab
2024-02-29 18:33 ` dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:07 ` dpdklab
2024-02-29 19:08 ` dpdklab
2024-02-29 19:18 ` dpdklab
2024-02-29 19:18 ` dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:20 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-02-29 19:52 ` dpdklab
2024-02-29 20:22 ` dpdklab
2024-02-29 20:22 ` dpdklab
2024-02-29 20:32 ` dpdklab
2024-02-29 20:32 ` dpdklab
2024-02-29 20:33 ` dpdklab
2024-02-29 20:33 ` dpdklab
2024-02-29 20:33 ` dpdklab
2024-02-29 20:35 ` dpdklab
2024-02-29 20:35 ` dpdklab
2024-02-29 20:35 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:37 ` dpdklab
2024-02-29 20:37 ` dpdklab
2024-02-29 20:38 ` dpdklab
2024-02-29 20:38 ` dpdklab
2024-02-29 20:38 ` dpdklab
2024-02-29 20:39 ` dpdklab
2024-02-29 20:39 ` dpdklab
2024-02-29 20:40 ` dpdklab
2024-02-29 20:40 ` dpdklab
2024-02-29 20:41 ` dpdklab
2024-02-29 20:41 ` dpdklab
2024-02-29 20:42 ` dpdklab
2024-02-29 20:42 ` dpdklab
2024-02-29 20:43 ` dpdklab
2024-02-29 20:43 ` dpdklab
2024-02-29 20:43 ` dpdklab
2024-02-29 20:43 ` dpdklab
2024-02-29 20:44 ` dpdklab
2024-02-29 20:44 ` dpdklab
2024-02-29 20:44 ` dpdklab
2024-02-29 20:45 ` dpdklab
2024-02-29 20:45 ` dpdklab
2024-02-29 20:46 ` dpdklab
2024-02-29 20:47 ` dpdklab
2024-02-29 20:48 ` dpdklab
2024-02-29 20:49 ` dpdklab
2024-02-29 20:49 ` dpdklab
2024-02-29 20:50 ` dpdklab
2024-02-29 20:50 ` dpdklab
2024-02-29 20:51 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 22:17 ` dpdklab
2024-03-01 3:58 ` dpdklab
2024-03-01 8:51 ` dpdklab
2024-03-01 8:56 ` dpdklab
2024-03-01 9:02 ` dpdklab
2024-03-01 9:08 ` dpdklab
2024-03-02 9:04 ` dpdklab
2024-03-03 11:14 ` dpdklab [this message]
2024-03-03 11:47 ` dpdklab
2024-03-03 12:19 ` 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=65e45bae.170a0220.3ec81.028fSMTPIN_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).