From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137212-137225 [PATCH] [v5,14/14] net/cnxk: fix mbuf fiel
Date: Tue, 27 Feb 2024 19:04:06 -0800 (PST) [thread overview]
Message-ID: <65dea2a6.a70a0220.2a213.2810SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240226133536.2456406-14-ndabilpuram@marvell.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137225
_Performance Testing PASS_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Monday, February 26 2024 13:35:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c
137212-137225 --> 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 | -2.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 2.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29267/
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-28 3:04 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240226133536.2456406-14-ndabilpuram@marvell.com>
2024-02-26 13:15 ` |SUCCESS| pw137212-137225 [PATCH v5 14/14] net/cnxk: fix mbuf fields in multi-seg Tx path qemudev
2024-02-26 13:19 ` qemudev
2024-02-26 13:37 ` |SUCCESS| pw137225 " checkpatch
2024-02-26 14:45 ` 0-day Robot
2024-02-28 3:04 ` dpdklab [this message]
2024-02-28 3:11 ` |SUCCESS| pw137212-137225 [PATCH] [v5,14/14] net/cnxk: fix mbuf fiel dpdklab
2024-02-28 3:12 ` dpdklab
2024-02-27 0:00 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 22:37 dpdklab
2024-02-26 22:34 dpdklab
2024-02-26 22:09 dpdklab
2024-02-26 20:54 dpdklab
2024-02-26 20:26 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:22 dpdklab
2024-02-26 20:20 dpdklab
2024-02-26 20:17 dpdklab
2024-02-26 20:15 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:53 dpdklab
2024-02-26 19:53 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:51 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:48 dpdklab
2024-02-26 19:46 dpdklab
2024-02-26 19:38 dpdklab
2024-02-26 19:36 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:31 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:26 dpdklab
2024-02-26 19:25 dpdklab
2024-02-26 19:18 dpdklab
2024-02-26 19:17 dpdklab
2024-02-26 19:11 dpdklab
2024-02-26 19:11 dpdklab
2024-02-26 19:10 dpdklab
2024-02-26 19:10 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:08 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:01 dpdklab
2024-02-26 19:00 dpdklab
2024-02-26 18:57 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=65dea2a6.a70a0220.2a213.2810SMTPIN_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).