From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw106981 [PATCH] net/mlx5: fix inline length for multi-segment TSO
Date: Mon, 7 Feb 2022 18:13:33 +0000 (UTC) [thread overview]
Message-ID: <20220207181333.8CD9560461@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2674 bytes --]
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/106981
_Performance Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Monday, February 07 2022 15:48:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0e4dc6af06228c8504a5538512cb31ed7bf6cc23
106981 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | -1.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 2.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 1.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 0.9% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20933/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-07 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-08 7:13 dpdklab
2022-02-07 19:07 dpdklab
2022-02-07 18:57 dpdklab
2022-02-07 18:54 dpdklab
2022-02-07 18:54 dpdklab
2022-02-07 18:17 dpdklab
2022-02-07 18:13 dpdklab
2022-02-07 18:07 dpdklab
2022-02-07 18:07 dpdklab
2022-02-07 18:04 dpdklab
2022-02-07 18:00 dpdklab
2022-02-07 17:58 dpdklab
2022-02-07 17:58 dpdklab
[not found] <20220207154856.574542-1-dsosnowski@nvidia.com>
2022-02-07 15:50 ` checkpatch
2022-02-07 17:39 ` 0-day Robot
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=20220207181333.8CD9560461@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).