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| pw48345 [PATCH] ip_frag: fix ipv6 when MTU sizes not aligned to 8 bytes
Date: Mon, 26 Nov 2018 21:36:29 -0800 (PST) [thread overview]
Message-ID: <5bfcd7dd.1c69fb81.72fab.de3cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3810 bytes --]
Test-Label: mellanox-Performance-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/48345
_Performance Testing PASS_
Submitter: Chas Williams <3chas3@gmail.com>
Date: Tuesday, November 27 2018 04:56:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:43d162bc168e5c66346acf9f464495a088a5a9f0
48345 --> 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.031 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.204 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.155 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.004 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.013 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.001 |
+------------+---------+-------------------------------------+
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.064 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.001 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.056 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.121 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.082 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.057 |
+------------+---------+-------------------------------------+
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.123 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.013 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.056 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.007 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.005 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.001 |
+------------+---------+-------------------------------------+
UNH-IOL DPDK Performance Test Lab
next reply other threads:[~2018-11-27 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 5:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-27 5:36 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=5bfcd7dd.1c69fb81.72fab.de3cSMTPIN_ADDED_MISSING@mx.google.com \
--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).