From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134161 [PATCH] maintainers: Adding new maintainer to Nvi
Date: Mon, 13 Nov 2023 08:36:00 -0800 (PST) [thread overview]
Message-ID: <65525070.df0a0220.67f47.3c2aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/134161
_Performance Testing PASS_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Monday, November 13 2023 14:55:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df
134161 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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/28355/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-13 16:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 16:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 17:21 dpdklab
2023-11-15 17:02 dpdklab
2023-11-13 23:36 dpdklab
2023-11-13 20:10 dpdklab
2023-11-13 20:05 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 17:47 dpdklab
2023-11-13 17:28 dpdklab
2023-11-13 17:27 dpdklab
2023-11-13 17:26 dpdklab
2023-11-13 17:24 dpdklab
2023-11-13 17:24 dpdklab
2023-11-13 17:24 dpdklab
2023-11-13 17:23 dpdklab
2023-11-13 17:22 dpdklab
2023-11-13 17:22 dpdklab
2023-11-13 17:22 dpdklab
2023-11-13 17:22 dpdklab
2023-11-13 17:18 dpdklab
2023-11-13 17:16 dpdklab
2023-11-13 17:16 dpdklab
2023-11-13 17:11 dpdklab
2023-11-13 17:11 dpdklab
2023-11-13 17:11 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 17:10 dpdklab
2023-11-13 17:09 dpdklab
2023-11-13 16:59 dpdklab
2023-11-13 16:53 dpdklab
2023-11-13 16:53 dpdklab
2023-11-13 16:52 dpdklab
2023-11-13 16:52 dpdklab
2023-11-13 16:43 dpdklab
2023-11-13 16:42 dpdklab
2023-11-13 16:42 dpdklab
2023-11-13 16:40 dpdklab
2023-11-13 16:40 dpdklab
2023-11-13 16:40 dpdklab
2023-11-13 16:40 dpdklab
2023-11-13 16:39 dpdklab
2023-11-13 16:34 dpdklab
2023-11-13 16:13 dpdklab
2023-11-13 16:11 dpdklab
2023-11-13 16:11 dpdklab
2023-11-13 16:09 dpdklab
2023-11-13 16:07 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=65525070.df0a0220.67f47.3c2aSMTPIN_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).