From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136853-136855 [PATCH] [3/3] net/ionic: add vdev support
Date: Fri, 16 Feb 2024 09:44:07 -0800 (PST) [thread overview]
Message-ID: <65cf9ee7.050a0220.19147.0f68SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136855
_Performance Testing PASS_
Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Friday, February 16 2024 17:07:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d9d436f263a3f4313ad4c029a9905d6be6cbd6
136853-136855 --> 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 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29174/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-16 17:44 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 3:54 dpdklab
2024-02-17 3:47 dpdklab
2024-02-16 20:24 dpdklab
2024-02-16 20:18 dpdklab
2024-02-16 20:17 dpdklab
2024-02-16 20:14 dpdklab
2024-02-16 20:11 dpdklab
2024-02-16 20:07 dpdklab
2024-02-16 20:07 dpdklab
2024-02-16 20:05 dpdklab
2024-02-16 20:04 dpdklab
2024-02-16 20:03 dpdklab
2024-02-16 20:02 dpdklab
2024-02-16 19:16 dpdklab
2024-02-16 18:37 dpdklab
2024-02-16 18:37 dpdklab
2024-02-16 18:36 dpdklab
2024-02-16 18:32 dpdklab
2024-02-16 18:32 dpdklab
2024-02-16 18:31 dpdklab
2024-02-16 18:30 dpdklab
2024-02-16 18:29 dpdklab
2024-02-16 18:29 dpdklab
2024-02-16 18:29 dpdklab
2024-02-16 18:28 dpdklab
2024-02-16 18:27 dpdklab
2024-02-16 18:27 dpdklab
2024-02-16 18:26 dpdklab
2024-02-16 18:25 dpdklab
2024-02-16 18:25 dpdklab
2024-02-16 18:25 dpdklab
2024-02-16 18:24 dpdklab
2024-02-16 18:23 dpdklab
2024-02-16 18:14 dpdklab
2024-02-16 18:10 dpdklab
2024-02-16 18:09 dpdklab
2024-02-16 18:09 dpdklab
2024-02-16 18:09 dpdklab
2024-02-16 18:08 dpdklab
2024-02-16 18:08 dpdklab
2024-02-16 18:07 dpdklab
2024-02-16 18:07 dpdklab
2024-02-16 18:07 dpdklab
2024-02-16 18:05 dpdklab
2024-02-16 18:04 dpdklab
2024-02-16 18:04 dpdklab
2024-02-16 18:03 dpdklab
2024-02-16 18:03 dpdklab
2024-02-16 18:02 dpdklab
2024-02-16 18:02 dpdklab
2024-02-16 18:01 dpdklab
2024-02-16 18:01 dpdklab
2024-02-16 18:00 dpdklab
2024-02-16 18:00 dpdklab
2024-02-16 17:57 dpdklab
2024-02-16 17:57 dpdklab
2024-02-16 17:56 dpdklab
2024-02-16 17:56 dpdklab
2024-02-16 17:56 dpdklab
2024-02-16 17:55 dpdklab
2024-02-16 17:53 dpdklab
2024-02-16 17:48 dpdklab
2024-02-16 17:47 dpdklab
2024-02-16 17:47 dpdklab
2024-02-16 17:45 dpdklab
2024-02-16 17: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=65cf9ee7.050a0220.19147.0f68SMTPIN_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).