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| pw70332 [PATCH] lib/librte_net: fix bug for checksum calculating
Date: Fri, 15 May 2020 13:46:52 -0400 (EDT) [thread overview]
Message-ID: <20200515174652.7A39B6D421@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Test-Label: iol-nxp-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/70332
_Performance Testing PASS_
Submitter: guohongzhi <guohongzhi1@huawei.com>
Date: Friday, May 15 2020 13:08:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a8b8a863179e0a8478d488bb8545e632ed163456
70332 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.14.122
Compiler: 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.023 |
+------------+---------+-------------------------------------+
| 64 | 2048 | 0.039 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11155/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-05-15 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 17:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 11:59 dpdklab
2020-05-15 17:29 dpdklab
[not found] <20200515130850.12760-1-guohongzhi1@huawei.com>
2020-05-15 13:09 ` 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=20200515174652.7A39B6D421@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).