From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware
Date: Tue, 27 Aug 2024 09:29:51 -0700 (PDT) [thread overview]
Message-ID: <66cdfeff.050a0220.251a56.4ba3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240827151014.201-3-vipin.varghese@amd.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/143404
_Performance Testing PASS_
Submitter: Varghese, Vipin <vipin.varghese@amd.com>
Date: Tuesday, August 27 2024 15:10:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143403-143404 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#177294
Test environment and result as below:
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.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
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.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30863/
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-08-27 16:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240827151014.201-3-vipin.varghese@amd.com>
2024-08-27 14:44 ` |SUCCESS| pw143403-143404 [RFC 2/2] eal/lcore: add llc aware for each macro qemudev
2024-08-27 14:48 ` qemudev
2024-08-27 15:12 ` |WARNING| pw143404 " checkpatch
2024-08-27 15:54 ` |SUCCESS| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware dpdklab
2024-08-27 15:55 ` dpdklab
2024-08-27 15:58 ` |FAILURE| " dpdklab
2024-08-27 15:58 ` |SUCCESS| " dpdklab
2024-08-27 15:59 ` |FAILURE| " dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 15:59 ` dpdklab
2024-08-27 16:00 ` dpdklab
2024-08-27 16:09 ` dpdklab
2024-08-27 16:10 ` dpdklab
2024-08-27 16:12 ` dpdklab
2024-08-27 16:14 ` |SUCCESS| " dpdklab
2024-08-27 16:16 ` dpdklab
2024-08-27 16:17 ` |FAILURE| " dpdklab
2024-08-27 16:20 ` |WARNING| " dpdklab
2024-08-27 16:24 ` |SUCCESS| " dpdklab
2024-08-27 16:29 ` dpdklab [this message]
2024-08-27 16:41 ` |WARNING| " dpdklab
2024-08-27 16:43 ` |FAILURE| pw143404 [RFC 2/2] eal/lcore: add llc aware for each macro 0-day Robot
2024-08-27 16:43 ` |SUCCESS| pw143403-143404 [PATCH] [RFC,2/2] eal/lcore: add llc aware dpdklab
2024-08-27 17:04 ` |WARNING| " dpdklab
2024-08-27 19:51 ` |SUCCESS| " dpdklab
2024-09-19 23:23 ` dpdklab
2024-09-19 23:43 ` 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=66cdfeff.050a0220.251a56.4ba3SMTPIN_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).