From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130334 [PATCH] [v1,1/3] ethdev: introduce maximum Rx buf
Date: Tue, 15 Aug 2023 07:23:52 -0700 (PDT) [thread overview]
Message-ID: <64db8a78.050a0220.3159.7ff3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/130334
_Performance Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tuesday, August 15 2023 11:10:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
130334 --> performance testing pass
Test environment and result as below:
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27342/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-15 14:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 14:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 16:57 dpdklab
2023-08-15 16:31 dpdklab
2023-08-15 15:56 dpdklab
2023-08-15 15:47 dpdklab
2023-08-15 15:39 dpdklab
2023-08-15 15:35 dpdklab
2023-08-15 15:19 dpdklab
2023-08-15 15:17 dpdklab
2023-08-15 15:15 dpdklab
2023-08-15 15:14 dpdklab
2023-08-15 15:06 dpdklab
2023-08-15 14:59 dpdklab
2023-08-15 14:59 dpdklab
2023-08-15 14:57 dpdklab
2023-08-15 14:56 dpdklab
2023-08-15 14:55 dpdklab
2023-08-15 14:54 dpdklab
2023-08-15 14:52 dpdklab
2023-08-15 14:52 dpdklab
2023-08-15 14:51 dpdklab
2023-08-15 14:50 dpdklab
2023-08-15 14:48 dpdklab
2023-08-15 14:48 dpdklab
2023-08-15 14:46 dpdklab
2023-08-15 14:45 dpdklab
2023-08-15 14:45 dpdklab
2023-08-15 14:44 dpdklab
2023-08-15 14:44 dpdklab
2023-08-15 14:43 dpdklab
2023-08-15 14:42 dpdklab
2023-08-15 14:41 dpdklab
2023-08-15 14:39 dpdklab
2023-08-15 14:37 dpdklab
2023-08-15 14:37 dpdklab
2023-08-15 14:34 dpdklab
2023-08-15 14:32 dpdklab
2023-08-15 14:32 dpdklab
2023-08-15 14:31 dpdklab
2023-08-15 14:31 dpdklab
2023-08-15 14:27 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:26 dpdklab
2023-08-15 14:25 dpdklab
2023-08-15 14:24 dpdklab
2023-08-15 14:23 dpdklab
2023-08-15 14:19 dpdklab
2023-08-15 14:19 dpdklab
2023-08-15 14:18 dpdklab
2023-08-15 14:17 dpdklab
2023-08-15 14:16 dpdklab
2023-08-15 14:16 dpdklab
2023-08-15 14:15 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=64db8a78.050a0220.3159.7ff3SMTPIN_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).