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| pw64672-64676 [PATCH] [v4, 1/5] ipsec: move ipsec sad name length into .h
Date: Tue, 14 Jan 2020 21:49:09 -0500 (EST) [thread overview]
Message-ID: <20200115024909.AABA0A7A2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3955 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/64672
_Performance Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Tuesday, January 14 2020 14:27:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31bb45bcfdf5d67737eab17747b383775c9c36ae
64672-64676 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
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.458 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.091 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.073 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.015 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.008 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
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.205 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.088 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.012 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.002 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.001 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.011 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
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 | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | -0.179 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.229 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.017 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.083 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.091 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.028 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/9193/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-01-15 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 2:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 2:49 dpdklab
2020-01-15 0:01 dpdklab
2020-01-14 23:35 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=20200115024909.AABA0A7A2@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).