From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133866 [PATCH] net/mlx5: fix null derefrence in mlx5 txq
Date: Sat, 04 Nov 2023 00:22:06 -0700 (PDT) [thread overview]
Message-ID: <6545f11e.0d0a0220.e3786.e4aaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/133866
_Performance Testing PASS_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Saturday, November 04 2023 04:06:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:34c0c38ab772e8eea5243f530866d5b68519e7c7
133866 --> 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28238/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-04 7:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 7:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 11:28 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 9:39 dpdklab
2023-11-04 9:16 dpdklab
2023-11-04 9:13 dpdklab
2023-11-04 9:12 dpdklab
2023-11-04 9:11 dpdklab
2023-11-04 9:11 dpdklab
2023-11-04 9:10 dpdklab
2023-11-04 9:10 dpdklab
2023-11-04 9:09 dpdklab
2023-11-04 9:09 dpdklab
2023-11-04 9:08 dpdklab
2023-11-04 9:08 dpdklab
2023-11-04 9:08 dpdklab
2023-11-04 9:08 dpdklab
2023-11-04 9:07 dpdklab
2023-11-04 9:07 dpdklab
2023-11-04 9:06 dpdklab
2023-11-04 9:06 dpdklab
2023-11-04 9:06 dpdklab
2023-11-04 9:05 dpdklab
2023-11-04 9:05 dpdklab
2023-11-04 9:05 dpdklab
2023-11-04 9:05 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:00 dpdklab
2023-11-04 8:59 dpdklab
2023-11-04 8:59 dpdklab
2023-11-04 7:23 dpdklab
2023-11-04 7:11 dpdklab
2023-11-04 7:08 dpdklab
2023-11-04 7:07 dpdklab
2023-11-04 7:07 dpdklab
2023-11-04 7:07 dpdklab
2023-11-04 7:06 dpdklab
2023-11-04 7:05 dpdklab
2023-11-04 6:58 dpdklab
2023-11-04 6:58 dpdklab
2023-11-04 6:58 dpdklab
2023-11-04 6:58 dpdklab
2023-11-04 6:57 dpdklab
2023-11-04 6:56 dpdklab
2023-11-04 6:55 dpdklab
2023-11-04 6:55 dpdklab
2023-11-04 6:55 dpdklab
2023-11-04 6:54 dpdklab
2023-11-04 6:49 dpdklab
2023-11-04 6:48 dpdklab
2023-11-04 6:48 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=6545f11e.0d0a0220.e3786.e4aaSMTPIN_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).