From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144353 [PATCH] net/mana: support rdma-core via pkg-confi
Date: Fri, 20 Sep 2024 07:30:22 -0700 (PDT) [thread overview]
Message-ID: <66ed86fe.050a0220.2bb19e.980fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240920111116.1486095-1-16567adigashreesh@gmail.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/144353
_Performance Testing PASS_
Submitter: Shreesh Adiga <16567adigashreesh@gmail.com>
Date: Friday, September 20 2024 11:11:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5
144353 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#182599
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
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.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31098/
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-09-20 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920111116.1486095-1-16567adigashreesh@gmail.com>
2024-09-20 10:43 ` |SUCCESS| pw144353 [PATCH] net/mana: support rdma-core via pkg-config in meson qemudev
2024-09-20 10:48 ` qemudev
2024-09-20 11:12 ` checkpatch
2024-09-20 12:04 ` 0-day Robot
2024-09-20 14:30 ` dpdklab [this message]
2024-09-20 14:33 ` |PENDING| pw144353 [PATCH] net/mana: support rdma-core via pkg-confi dpdklab
2024-09-20 14:38 ` |SUCCESS| " dpdklab
2024-09-20 14:41 ` dpdklab
2024-09-20 14:42 ` dpdklab
2024-09-20 14:44 ` |PENDING| " dpdklab
2024-09-20 14:46 ` |SUCCESS| " dpdklab
2024-09-20 14:50 ` |PENDING| " dpdklab
2024-09-21 13:19 ` |SUCCESS| " dpdklab
2024-09-23 10:43 ` dpdklab
2024-09-23 12:03 ` 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=66ed86fe.050a0220.2bb19e.980fSMTPIN_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).