From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137812 [PATCH] eal/x86: improve rte_memcpy const size 16
Date: Wed, 06 Mar 2024 12:46:00 -0800 (PST) [thread overview]
Message-ID: <65e8d608.170a0220.f3edb.4a90SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240302234812.9137-1-mb@smartsharesystems.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137812
_Performance Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Saturday, March 02 2024 23:48:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364
137812 --> 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 | 1.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29390/
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-03-06 20:46 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240302234812.9137-1-mb@smartsharesystems.com>
2024-03-02 23:25 ` |SUCCESS| pw137812 [PATCH] eal/x86: improve rte_memcpy const size 16 performance qemudev
2024-03-02 23:29 ` qemudev
2024-03-02 23:48 ` checkpatch
2024-03-03 0:17 ` |SUCCESS| pw137812 [PATCH] eal/x86: improve rte_memcpy const size 16 dpdklab
2024-03-03 0:17 ` dpdklab
2024-03-03 0:18 ` dpdklab
2024-03-03 0:18 ` dpdklab
2024-03-03 0:18 ` dpdklab
2024-03-03 0:19 ` dpdklab
2024-03-03 0:20 ` dpdklab
2024-03-03 0:21 ` dpdklab
2024-03-03 0:21 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:23 ` dpdklab
2024-03-03 0:23 ` dpdklab
2024-03-03 0:24 ` dpdklab
2024-03-03 0:24 ` dpdklab
2024-03-03 0:25 ` dpdklab
2024-03-03 0:26 ` |FAILURE| " dpdklab
2024-03-03 0:26 ` |SUCCESS| " dpdklab
2024-03-03 0:27 ` dpdklab
2024-03-03 0:27 ` dpdklab
2024-03-03 0:28 ` dpdklab
2024-03-03 0:28 ` dpdklab
2024-03-03 0:28 ` dpdklab
2024-03-03 0:29 ` dpdklab
2024-03-03 0:29 ` dpdklab
2024-03-03 0:29 ` dpdklab
2024-03-03 0:30 ` dpdklab
2024-03-03 0:32 ` dpdklab
2024-03-03 0:32 ` dpdklab
2024-03-03 0:33 ` dpdklab
2024-03-03 0:34 ` dpdklab
2024-03-03 0:34 ` dpdklab
2024-03-03 0:34 ` dpdklab
2024-03-03 0:35 ` dpdklab
2024-03-03 0:36 ` dpdklab
2024-03-03 0:37 ` dpdklab
2024-03-03 0:37 ` dpdklab
2024-03-03 0:37 ` dpdklab
2024-03-03 0:39 ` dpdklab
2024-03-03 0:39 ` dpdklab
2024-03-03 0:40 ` dpdklab
2024-03-03 0:40 ` dpdklab
2024-03-03 0:40 ` dpdklab
2024-03-03 0:41 ` dpdklab
2024-03-03 0:41 ` dpdklab
2024-03-03 0:42 ` dpdklab
2024-03-03 0:44 ` |SUCCESS| pw137812 [PATCH] eal/x86: improve rte_memcpy const size 16 performance 0-day Robot
2024-03-03 0:47 ` |SUCCESS| pw137812 [PATCH] eal/x86: improve rte_memcpy const size 16 dpdklab
2024-03-03 0:48 ` dpdklab
2024-03-03 0:48 ` dpdklab
2024-03-03 0:49 ` dpdklab
2024-03-03 0:50 ` dpdklab
2024-03-03 0:50 ` dpdklab
2024-03-03 0:50 ` dpdklab
2024-03-03 0:52 ` dpdklab
2024-03-03 0:53 ` dpdklab
2024-03-03 0:53 ` dpdklab
2024-03-03 0:55 ` dpdklab
2024-03-03 0:58 ` dpdklab
2024-03-03 0:58 ` dpdklab
2024-03-03 1:01 ` dpdklab
2024-03-03 1:02 ` dpdklab
2024-03-03 1:03 ` dpdklab
2024-03-03 1:04 ` dpdklab
2024-03-03 1:04 ` dpdklab
2024-03-03 1:05 ` dpdklab
2024-03-03 1:09 ` dpdklab
2024-03-03 1:09 ` dpdklab
2024-03-03 1:09 ` dpdklab
2024-03-03 1:10 ` dpdklab
2024-03-03 1:10 ` dpdklab
2024-03-03 1:10 ` dpdklab
2024-03-03 1:13 ` dpdklab
2024-03-03 1:13 ` dpdklab
2024-03-03 1:18 ` dpdklab
2024-03-03 1:23 ` dpdklab
2024-03-03 1:24 ` dpdklab
2024-03-03 1:27 ` dpdklab
2024-03-03 1:50 ` dpdklab
2024-03-03 7:27 ` dpdklab
2024-03-06 19:08 ` dpdklab
2024-03-06 19:48 ` dpdklab
2024-03-06 20:10 ` dpdklab
2024-03-06 20:46 ` dpdklab [this message]
2024-03-06 21:18 ` dpdklab
2024-03-06 21: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=65e8d608.170a0220.f3edb.4a90SMTPIN_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).