From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133316 [PATCH] net/mlx5/hws: fix integrity bits level
Date: Wed, 25 Oct 2023 19:44:35 -0700 (PDT) [thread overview]
Message-ID: <6539d293.170a0220.9a13a.39cbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/133316
_Performance Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Wednesday, October 25 2023 20:41:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133316 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28075/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-26 2:44 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-27 21:35 dpdklab
2023-10-26 17:59 dpdklab
2023-10-26 17:50 dpdklab
2023-10-26 17:11 dpdklab
2023-10-26 17:03 dpdklab
2023-10-26 4:35 dpdklab
2023-10-26 3:53 dpdklab
2023-10-26 3:42 dpdklab
2023-10-26 3:41 dpdklab
2023-10-26 3:40 dpdklab
2023-10-26 3:39 dpdklab
2023-10-26 3:38 dpdklab
2023-10-26 3:37 dpdklab
2023-10-26 3:37 dpdklab
2023-10-26 3:36 dpdklab
2023-10-26 3:36 dpdklab
2023-10-26 3:36 dpdklab
2023-10-26 3:36 dpdklab
2023-10-26 3:36 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:35 dpdklab
2023-10-26 3:34 dpdklab
2023-10-26 3:34 dpdklab
2023-10-26 3:34 dpdklab
2023-10-26 3:34 dpdklab
2023-10-26 3:33 dpdklab
2023-10-26 3:33 dpdklab
2023-10-26 3:32 dpdklab
2023-10-26 3:32 dpdklab
2023-10-26 3:31 dpdklab
2023-10-26 3:31 dpdklab
2023-10-26 3:31 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:30 dpdklab
2023-10-26 3:29 dpdklab
2023-10-26 3:29 dpdklab
2023-10-26 3:28 dpdklab
2023-10-26 3:28 dpdklab
2023-10-26 3:14 dpdklab
2023-10-26 3:13 dpdklab
2023-10-26 3:11 dpdklab
2023-10-26 3:01 dpdklab
2023-10-26 2:55 dpdklab
[not found] <20231025204101.1604238-1-akozyrev@nvidia.com>
2023-10-25 20:27 ` qemudev
2023-10-25 20:32 ` qemudev
2023-10-25 20:43 ` checkpatch
2023-10-25 21:59 ` 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=6539d293.170a0220.9a13a.39cbSMTPIN_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).