From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135189 [PATCH] [v5] lib/net: fix tcp/udp cksum with padd
Date: Thu, 14 Dec 2023 02:56:23 -0800 (PST) [thread overview]
Message-ID: <657adf57.170a0220.64c2a.6962SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135189
_Performance Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Thursday, December 14 2023 09:22:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135189 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28620/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-14 10:56 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 10:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 14:18 dpdklab
2023-12-14 14:16 dpdklab
2023-12-14 14:03 dpdklab
2023-12-14 13:46 dpdklab
2023-12-14 12:38 dpdklab
2023-12-14 12:38 dpdklab
2023-12-14 12:34 dpdklab
2023-12-14 12:29 dpdklab
2023-12-14 12:13 dpdklab
2023-12-14 12:07 dpdklab
2023-12-14 12:05 dpdklab
2023-12-14 12:04 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:01 dpdklab
2023-12-14 12:00 dpdklab
2023-12-14 11:58 dpdklab
2023-12-14 11:58 dpdklab
2023-12-14 11:50 dpdklab
2023-12-14 11:43 dpdklab
2023-12-14 11:42 dpdklab
2023-12-14 11:41 dpdklab
2023-12-14 11:41 dpdklab
2023-12-14 11:36 dpdklab
2023-12-14 11:35 dpdklab
2023-12-14 11:34 dpdklab
2023-12-14 11:33 dpdklab
2023-12-14 11:33 dpdklab
2023-12-14 11:25 dpdklab
2023-12-14 11:24 dpdklab
2023-12-14 11:21 dpdklab
2023-12-14 11:20 dpdklab
2023-12-14 11:20 dpdklab
2023-12-14 11:18 dpdklab
2023-12-14 11:17 dpdklab
2023-12-14 11:16 dpdklab
2023-12-14 11:15 dpdklab
2023-12-14 11:12 dpdklab
2023-12-14 11:11 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:08 dpdklab
2023-12-14 11:07 dpdklab
2023-12-14 11:07 dpdklab
2023-12-14 11:07 dpdklab
2023-12-14 11:06 dpdklab
2023-12-14 11:05 dpdklab
2023-12-14 11:05 dpdklab
2023-12-14 10:56 dpdklab
2023-12-14 10:56 dpdklab
2023-12-14 10:55 dpdklab
2023-12-14 10:53 dpdklab
2023-12-14 10:53 dpdklab
2023-12-14 10:53 dpdklab
2023-12-14 10:50 dpdklab
2023-12-14 10:50 dpdklab
2023-12-14 10:49 dpdklab
2023-12-14 10:49 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=657adf57.170a0220.64c2a.6962SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).