From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@mellanox.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw55527 [PATCH] [v3] net: fix the way how L4 checksum choice is tested
Date: Fri, 28 Jun 2019 15:30:29 -0400 (EDT) [thread overview]
Message-ID: <20190628193029.2C1A0DF566@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3975 bytes --]
Test-Label: mellanox-Performance-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/55527
_Performance Testing PASS_
Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: Friday, June 28 2019 03:13:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:28b2d3d112e2bde5264921d8feca89e2e5708a87
55527 --> performance testing pass
Test environment and result as below:
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.417 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.228 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.162 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.025 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.022 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.014 |
+------------+---------+-------------------------------------+
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.458 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.215 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.202 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.003 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.046 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.031 |
+------------+---------+-------------------------------------+
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.449 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.044 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.029 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.147 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.013 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.014 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/6320/
UNH-IOL DPDK Performance Test Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2019-06-28 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 19:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-28 19:30 dpdklab
[not found] <20190628031309.24215-1-ivan.malov@oktetlabs.ru>
2019-06-28 3:14 ` [dpdk-test-report] |SUCCESS| pw55527 [PATCH v3] " checkpatch
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=20190628193029.2C1A0DF566@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.com \
--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).