From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbar
Date: Thu, 14 Nov 2024 06:40:48 -0800 (PST) [thread overview]
Message-ID: <67360bf0.4a0a0220.3424b9.2bbdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/148475
_Performance Testing PASS_
Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Thursday, November 14 2024 08:37:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148475 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#196481
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31930/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-11-14 14:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
2024-11-14 8:05 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init() qemudev
2024-11-14 8:09 ` qemudev
2024-11-14 8:39 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init checkpatch
2024-11-14 11:05 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init() 0-day Robot
2024-11-14 14:40 ` dpdklab [this message]
2024-11-14 14:42 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbar dpdklab
2024-11-14 14:50 ` dpdklab
2024-11-14 15:26 ` dpdklab
2024-11-14 16:00 ` dpdklab
2024-11-14 17:08 ` dpdklab
2024-11-14 17:15 ` dpdklab
2024-11-14 20:17 ` dpdklab
2024-11-14 21:00 ` dpdklab
2024-11-14 21:09 ` dpdklab
2024-11-14 21:42 ` |PENDING| " dpdklab
2024-11-14 22:53 ` dpdklab
2024-11-14 23:25 ` |WARNING| " dpdklab
2024-11-15 0:54 ` |SUCCESS| " 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=67360bf0.4a0a0220.3424b9.2bbdSMTPIN_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).