From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136205-136206 [PATCH] [2/2] net/mana: properly deal with
Date: Mon, 29 Jan 2024 23:24:19 -0800 (PST) [thread overview]
Message-ID: <65b8a423.0d0a0220.18c81.95adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136206
_Performance Testing PASS_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, January 30 2024 01:24:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:906d2c06b3cfc61620453c6909266fe771f8ccfb
136205-136206 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
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.6% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28982/
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-30 7:24 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 7:57 dpdklab
2024-01-30 7:36 dpdklab
2024-01-30 7:24 dpdklab
2024-01-30 7:13 dpdklab
2024-01-30 7:09 dpdklab
2024-01-30 7:05 dpdklab
2024-01-30 6:57 dpdklab
2024-01-30 6:55 dpdklab
2024-01-30 6:54 dpdklab
2024-01-30 6:51 dpdklab
2024-01-30 6:49 dpdklab
2024-01-30 6:41 dpdklab
2024-01-30 6:40 dpdklab
2024-01-30 6:40 dpdklab
2024-01-30 6:39 dpdklab
2024-01-30 6:38 dpdklab
2024-01-30 6:38 dpdklab
2024-01-30 6:37 dpdklab
2024-01-30 6:37 dpdklab
2024-01-30 6:37 dpdklab
2024-01-30 6:36 dpdklab
2024-01-30 6:36 dpdklab
2024-01-30 6:35 dpdklab
2024-01-30 6:35 dpdklab
2024-01-30 6:35 dpdklab
2024-01-30 6:34 dpdklab
2024-01-30 6:34 dpdklab
2024-01-30 6:28 dpdklab
2024-01-30 6:24 dpdklab
2024-01-30 6:24 dpdklab
2024-01-30 6:24 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:21 dpdklab
2024-01-30 6:20 dpdklab
2024-01-30 6:20 dpdklab
2024-01-30 6:19 dpdklab
2024-01-30 6:19 dpdklab
2024-01-30 6:17 dpdklab
2024-01-30 6:12 dpdklab
2024-01-30 6:12 dpdklab
2024-01-30 6:12 dpdklab
2024-01-30 6:12 dpdklab
2024-01-30 6:10 dpdklab
2024-01-30 6:08 dpdklab
2024-01-30 5:54 dpdklab
2024-01-30 5:53 dpdklab
2024-01-30 5:53 dpdklab
2024-01-30 5:53 dpdklab
2024-01-30 5:51 dpdklab
2024-01-30 5:50 dpdklab
2024-01-30 5:48 dpdklab
2024-01-30 5:48 dpdklab
2024-01-30 5:40 dpdklab
2024-01-30 5:40 dpdklab
2024-01-30 5:39 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:37 dpdklab
2024-01-30 5:36 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=65b8a423.0d0a0220.18c81.95adSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).