From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137319 [PATCH] [v2] build: make buffer headroom configur
Date: Thu, 29 Feb 2024 00:27:45 -0800 (PST) [thread overview]
Message-ID: <65e04001.170a0220.5c88a.9538SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240220145735.383949-1-Parthakumar.Roy@ibm.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137319
_Performance Testing PASS_
Submitter: Parthakumar Roy <partha.roy.tx@gmail.com>
Date: Tuesday, February 20 2024 14:57:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137319 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -3.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 1.9% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29276/
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-02-29 8:27 UTC|newest]
Thread overview: 142+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240220145735.383949-1-Parthakumar.Roy@ibm.com>
2024-02-27 6:01 ` |SUCCESS| pw137319 [PATCH v2] build: make buffer headroom configurable qemudev
2024-02-27 6:05 ` qemudev
2024-02-27 6:08 ` |WARNING| " checkpatch
2024-02-27 20:24 ` |SUCCESS| pw137319 [PATCH] [v2] build: make buffer headroom configur dpdklab
2024-02-28 2:40 ` dpdklab
2024-02-28 4:01 ` dpdklab
2024-02-28 4:23 ` dpdklab
2024-02-28 4:28 ` dpdklab
2024-02-28 4:46 ` dpdklab
2024-02-28 4:52 ` dpdklab
2024-02-28 7:51 ` dpdklab
2024-02-28 9:15 ` dpdklab
2024-02-29 8:27 ` dpdklab [this message]
2024-02-29 8:32 ` dpdklab
2024-02-29 8:37 ` dpdklab
2024-02-29 8:44 ` dpdklab
2024-02-29 8:49 ` dpdklab
2024-02-29 8:54 ` dpdklab
2024-02-29 8:59 ` dpdklab
2024-02-29 9:49 ` dpdklab
2024-02-27 11:51 dpdklab
2024-02-27 11:56 dpdklab
2024-02-27 11:58 dpdklab
2024-02-27 12:03 dpdklab
2024-02-27 12:04 dpdklab
2024-02-27 12:09 dpdklab
2024-02-27 12:10 dpdklab
2024-02-27 12:40 dpdklab
2024-02-27 12:50 dpdklab
2024-02-27 12:50 dpdklab
2024-02-27 12:52 dpdklab
2024-02-27 12:54 dpdklab
2024-02-27 12:56 dpdklab
2024-02-27 12:57 dpdklab
2024-02-27 12:57 dpdklab
2024-02-27 12:58 dpdklab
2024-02-27 12:58 dpdklab
2024-02-27 12:58 dpdklab
2024-02-27 12:59 dpdklab
2024-02-27 12:59 dpdklab
2024-02-27 13:00 dpdklab
2024-02-27 13:08 dpdklab
2024-02-27 13:08 dpdklab
2024-02-27 13:09 dpdklab
2024-02-27 13:09 dpdklab
2024-02-27 13:10 dpdklab
2024-02-27 13:11 dpdklab
2024-02-27 13:14 dpdklab
2024-02-27 13:46 dpdklab
2024-02-27 14:54 dpdklab
2024-02-27 14:55 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 15:02 dpdklab
2024-02-27 15:34 dpdklab
2024-02-27 15:35 dpdklab
2024-02-27 15:44 dpdklab
2024-02-27 15:46 dpdklab
2024-02-27 15:46 dpdklab
2024-02-27 15:48 dpdklab
2024-02-27 15:49 dpdklab
2024-02-27 15:51 dpdklab
2024-02-27 15:53 dpdklab
2024-02-27 15:54 dpdklab
2024-02-27 15:55 dpdklab
2024-02-27 15:57 dpdklab
2024-02-27 16:00 dpdklab
2024-02-27 16:00 dpdklab
2024-02-27 16:00 dpdklab
2024-02-27 16:00 dpdklab
2024-02-27 16:01 dpdklab
2024-02-27 16:01 dpdklab
2024-02-27 16:02 dpdklab
2024-02-27 16:02 dpdklab
2024-02-27 16:02 dpdklab
2024-02-27 16:02 dpdklab
2024-02-27 16:03 dpdklab
2024-02-27 16:03 dpdklab
2024-02-27 16:04 dpdklab
2024-02-27 16:04 dpdklab
2024-02-27 16:04 dpdklab
2024-02-27 16:04 dpdklab
2024-02-27 16:04 dpdklab
2024-02-27 16:05 dpdklab
2024-02-27 16:05 dpdklab
2024-02-27 16:05 dpdklab
2024-02-27 16:05 dpdklab
2024-02-27 16:06 dpdklab
2024-02-27 16:06 dpdklab
2024-02-27 16:07 dpdklab
2024-02-27 16:08 dpdklab
2024-02-27 16:09 dpdklab
2024-02-27 16:09 dpdklab
2024-02-27 16:09 dpdklab
2024-02-27 16:09 dpdklab
2024-02-27 16:10 dpdklab
2024-02-27 16:11 dpdklab
2024-02-27 16:11 dpdklab
2024-02-27 16:11 dpdklab
2024-02-27 16:12 dpdklab
2024-02-27 16:12 dpdklab
2024-02-27 16:13 dpdklab
2024-02-27 16:26 dpdklab
2024-02-27 16:27 dpdklab
2024-02-27 16:27 dpdklab
2024-02-27 16:33 dpdklab
2024-02-27 16:33 dpdklab
2024-02-27 16:33 dpdklab
2024-02-27 16:33 dpdklab
2024-02-27 16:34 dpdklab
2024-02-27 16:35 dpdklab
2024-02-27 16:35 dpdklab
2024-02-27 16:35 dpdklab
2024-02-27 16:36 dpdklab
2024-02-27 16:36 dpdklab
2024-02-27 16:40 dpdklab
2024-02-27 16:40 dpdklab
2024-02-27 16:40 dpdklab
2024-02-27 16:41 dpdklab
2024-02-27 16:41 dpdklab
2024-02-27 16:41 dpdklab
2024-02-27 16:42 dpdklab
2024-02-27 16:43 dpdklab
2024-02-27 16:43 dpdklab
2024-02-27 16:43 dpdklab
2024-02-27 16:45 dpdklab
2024-02-27 16:47 dpdklab
2024-02-27 16:47 dpdklab
2024-02-27 16:47 dpdklab
2024-02-27 16:48 dpdklab
2024-02-27 16:48 dpdklab
2024-02-27 16:48 dpdklab
2024-02-27 16:49 dpdklab
2024-02-27 16:50 dpdklab
2024-02-27 16:51 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:53 dpdklab
2024-02-27 16:53 dpdklab
2024-02-27 17:13 dpdklab
2024-02-27 17:30 dpdklab
2024-02-27 18:48 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=65e04001.170a0220.5c88a.9538SMTPIN_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).