From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136221 [PATCH] [v2] doc: update guideline for fix commit
Date: Tue, 30 Jan 2024 06:47:03 -0800 (PST) [thread overview]
Message-ID: <65b90be7.050a0220.7c3c4.549eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136221
_Performance Testing PASS_
Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Tuesday, January 30 2024 14:09:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ca7aa1af6c6ff32c2c5ad958e527e17d11f6d18
136221 --> 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/28992/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-30 14:47 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 14:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 17:32 dpdklab
2024-01-30 16:58 dpdklab
2024-01-30 16:20 dpdklab
2024-01-30 15:50 dpdklab
2024-01-30 15:38 dpdklab
2024-01-30 15:36 dpdklab
2024-01-30 15:34 dpdklab
2024-01-30 15:34 dpdklab
2024-01-30 15:32 dpdklab
2024-01-30 15:31 dpdklab
2024-01-30 15:30 dpdklab
2024-01-30 15:29 dpdklab
2024-01-30 15:26 dpdklab
2024-01-30 15:25 dpdklab
2024-01-30 15:25 dpdklab
2024-01-30 15:24 dpdklab
2024-01-30 15:21 dpdklab
2024-01-30 15:19 dpdklab
2024-01-30 15:19 dpdklab
2024-01-30 15:18 dpdklab
2024-01-30 15:17 dpdklab
2024-01-30 15:16 dpdklab
2024-01-30 15:16 dpdklab
2024-01-30 15:15 dpdklab
2024-01-30 15:15 dpdklab
2024-01-30 15:13 dpdklab
2024-01-30 15:13 dpdklab
2024-01-30 15:12 dpdklab
2024-01-30 15:12 dpdklab
2024-01-30 15:12 dpdklab
2024-01-30 15:10 dpdklab
2024-01-30 15:08 dpdklab
2024-01-30 15:08 dpdklab
2024-01-30 15:07 dpdklab
2024-01-30 15:05 dpdklab
2024-01-30 15:05 dpdklab
2024-01-30 15:03 dpdklab
2024-01-30 15:03 dpdklab
2024-01-30 15:01 dpdklab
2024-01-30 15:01 dpdklab
2024-01-30 15:01 dpdklab
2024-01-30 15:00 dpdklab
2024-01-30 14:59 dpdklab
2024-01-30 14:59 dpdklab
2024-01-30 14:59 dpdklab
2024-01-30 14:58 dpdklab
2024-01-30 14:58 dpdklab
2024-01-30 14:57 dpdklab
2024-01-30 14:54 dpdklab
2024-01-30 14:54 dpdklab
2024-01-30 14:53 dpdklab
2024-01-30 14:53 dpdklab
2024-01-30 14:52 dpdklab
2024-01-30 14:52 dpdklab
2024-01-30 14:51 dpdklab
2024-01-30 14:51 dpdklab
2024-01-30 14:49 dpdklab
2024-01-30 14:49 dpdklab
2024-01-30 14:49 dpdklab
2024-01-30 14:48 dpdklab
2024-01-30 14:48 dpdklab
2024-01-30 14:48 dpdklab
2024-01-30 14:48 dpdklab
2024-01-30 14:47 dpdklab
2024-01-30 14:46 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=65b90be7.050a0220.7c3c4.549eSMTPIN_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).