From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124436 [PATCH] common/idpf: fix Rx queue configuration
Date: Thu, 23 Feb 2023 04:18:46 +0000 (UTC) [thread overview]
Message-ID: <20230223041846.DAC20601B4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124436
_Performance Testing PASS_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Thursday, February 23 2023 03:16:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124436 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25526/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-23 4:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 4:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 20:39 dpdklab
2023-02-23 10:40 dpdklab
2023-02-23 7:26 dpdklab
2023-02-23 7:26 dpdklab
2023-02-23 7:20 dpdklab
2023-02-23 7:18 dpdklab
2023-02-23 7:16 dpdklab
2023-02-23 7:14 dpdklab
2023-02-23 7:13 dpdklab
2023-02-23 7:09 dpdklab
2023-02-23 7:08 dpdklab
2023-02-23 7:03 dpdklab
2023-02-23 7:02 dpdklab
2023-02-23 6:58 dpdklab
2023-02-23 6:48 dpdklab
2023-02-23 4:56 dpdklab
2023-02-23 4:43 dpdklab
2023-02-23 4:36 dpdklab
2023-02-23 4:35 dpdklab
2023-02-23 4:34 dpdklab
2023-02-23 4:31 dpdklab
2023-02-23 4:22 dpdklab
2023-02-23 4:19 dpdklab
2023-02-23 4:15 dpdklab
[not found] <20230223031646.11222-1-beilei.xing@intel.com>
2023-02-23 3:34 ` qemudev
2023-02-23 3:38 ` qemudev
2023-02-23 3:46 ` checkpatch
2023-02-23 6:39 ` 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=20230223041846.DAC20601B4@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).