From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124138-124140 [PATCH] [v2, 3/3] net/ark: resize data field to match fpga access
Date: Fri, 17 Feb 2023 22:40:12 +0000 (UTC) [thread overview]
Message-ID: <20230217224012.6A8A7600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124140
_Performance Testing PASS_
Submitter: Ed Czeck <ed.czeck@atomicrules.com>
Date: Friday, February 17 2023 21:59:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8a3ef4b89e6dd0247355fdf3a77ff7ec1db28d8d
124138-124140 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25446/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-17 22:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 22:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 0:57 dpdklab
2023-02-18 16:16 dpdklab
2023-02-18 0:08 dpdklab
2023-02-18 0:08 dpdklab
2023-02-18 0:06 dpdklab
2023-02-17 23:52 dpdklab
2023-02-17 23:52 dpdklab
2023-02-17 23:52 dpdklab
2023-02-17 23:50 dpdklab
2023-02-17 23:50 dpdklab
2023-02-17 23:49 dpdklab
2023-02-17 23:47 dpdklab
2023-02-17 23:46 dpdklab
2023-02-17 23:37 dpdklab
2023-02-17 23:21 dpdklab
2023-02-17 22:53 dpdklab
2023-02-17 22:49 dpdklab
2023-02-17 22:46 dpdklab
2023-02-17 22:45 dpdklab
2023-02-17 22:43 dpdklab
2023-02-17 22:42 dpdklab
2023-02-17 22:33 dpdklab
2023-02-17 22:32 dpdklab
2023-02-17 22:29 dpdklab
[not found] <20230217215923.2561685-3-ed.czeck@atomicrules.com>
2023-02-17 21:48 ` |SUCCESS| pw124138-124140 [PATCH v2 " qemudev
2023-02-17 21:52 ` qemudev
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=20230217224012.6A8A7600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).