From: dpdklab@iol.unh.edu
To: Ruoshan Shi <ruoshan.shi@nxp.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw64137 [PATCH] [v2] net/ice: fix TSO pkt exceeds allowed buf size issue
Date: Thu, 26 Dec 2019 03:00:55 -0500 (EST) [thread overview]
Message-ID: <20191226080055.5F731A7A2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Test-Label: iol-nxp-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/64137
_Performance Testing PASS_
Submitter: Xiaoyun Li <xiaoyun.li@intel.com>
Date: Thursday, December 26 2019 06:54:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2e088e6f94b773233c06440763c1be43d0d705b3
64137 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.14.122
GCC: 7.3.0
NIC: NXP LS2088A 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 512 | 0.065 |
+------------+---------+-------------------------------------+
| 64 | 2048 | 0.276 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/9029/
UNH-IOL DPDK Community Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2019-12-26 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 8:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-26 8:00 dpdklab
2019-12-26 7:42 dpdklab
2019-12-26 7:33 dpdklab
[not found] <20191226065428.64870-1-xiaoyun.li@intel.com>
2019-12-26 6:57 ` [dpdk-test-report] |SUCCESS| pw64137 [PATCH v2] " 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=20191226080055.5F731A7A2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ruoshan.shi@nxp.com \
--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).