From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135847-135848 [PATCH] [V1,2/2] net/mlx5: use traffic cla
Date: Fri, 12 Jan 2024 00:39:21 -0800 (PST) [thread overview]
Message-ID: <65a0fab9.020a0220.f8925.6ff2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135848
_Performance Testing PASS_
Submitter: Gavin Li <gavinl@nvidia.com>
Date: Friday, January 12 2024 07:50:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:30468d404a3447cae8797576e885b9831bb88391
135847-135848 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28852/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-12 8:39 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:39 dpdklab [this message]
2024-01-12 8:52 dpdklab
2024-01-12 8:53 dpdklab
2024-01-12 8:53 dpdklab
2024-01-12 8:53 dpdklab
2024-01-12 8:55 dpdklab
2024-01-12 8:55 dpdklab
2024-01-12 8:55 dpdklab
2024-01-12 8:56 dpdklab
2024-01-12 8:57 dpdklab
2024-01-12 8:58 dpdklab
2024-01-12 8:59 dpdklab
2024-01-12 8:59 dpdklab
2024-01-12 9:00 dpdklab
2024-01-12 9:01 dpdklab
2024-01-12 9:01 dpdklab
2024-01-12 9:02 dpdklab
2024-01-12 9:03 dpdklab
2024-01-12 9:04 dpdklab
2024-01-12 9:04 dpdklab
2024-01-12 9:10 dpdklab
2024-01-12 9:11 dpdklab
2024-01-12 9:12 dpdklab
2024-01-12 9:12 dpdklab
2024-01-12 9:13 dpdklab
2024-01-12 9:14 dpdklab
2024-01-12 9:14 dpdklab
2024-01-12 9:14 dpdklab
2024-01-12 9:15 dpdklab
2024-01-12 9:15 dpdklab
2024-01-12 9:16 dpdklab
2024-01-12 9:16 dpdklab
2024-01-12 9:16 dpdklab
2024-01-12 9:16 dpdklab
2024-01-12 9:17 dpdklab
2024-01-12 9:17 dpdklab
2024-01-12 9:17 dpdklab
2024-01-12 9:17 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:18 dpdklab
2024-01-12 9:19 dpdklab
2024-01-12 9:19 dpdklab
2024-01-12 9:19 dpdklab
2024-01-12 9:19 dpdklab
2024-01-12 9:20 dpdklab
2024-01-12 9:20 dpdklab
2024-01-12 9:20 dpdklab
2024-01-12 9:20 dpdklab
2024-01-12 9:21 dpdklab
2024-01-12 9:23 dpdklab
2024-01-12 9:23 dpdklab
2024-01-12 9:23 dpdklab
2024-01-12 9:23 dpdklab
2024-01-12 9:24 dpdklab
2024-01-12 9:24 dpdklab
2024-01-12 9:24 dpdklab
2024-01-12 9:24 dpdklab
2024-01-12 9:25 dpdklab
2024-01-12 9:25 dpdklab
2024-01-12 9:35 dpdklab
2024-01-12 9:38 dpdklab
2024-01-12 10:04 dpdklab
2024-01-12 10:26 dpdklab
2024-01-12 10:56 dpdklab
2024-01-12 11:48 dpdklab
2024-01-13 20:22 dpdklab
2024-01-13 20:30 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=65a0fab9.020a0220.f8925.6ff2SMTPIN_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).