From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97332 [PATCH] doc: announce change in dma mapping/unmapping
Date: Wed, 25 Aug 2021 10:59:41 -0400 (EDT) [thread overview]
Message-ID: <20210825145941.844E189060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/97332
_Performance Testing PASS_
Submitter: Xuan Ding <xuan.ding@intel.com>
Date: Wednesday, August 25 2021 11:27:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fdab8f2e17493192d555cd88cf28b06269174326
97332 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18346/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-25 14:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 14:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 1:24 dpdklab
2021-08-26 0:51 dpdklab
2021-08-26 0:26 dpdklab
2021-08-25 23:45 dpdklab
2021-08-25 18:37 dpdklab
2021-08-25 17:08 dpdklab
2021-08-25 16:47 dpdklab
2021-08-25 16:33 dpdklab
2021-08-25 16:17 dpdklab
2021-08-25 16:01 dpdklab
2021-08-25 15:44 dpdklab
2021-08-25 15:29 dpdklab
2021-08-25 15:14 dpdklab
2021-08-25 14:49 dpdklab
2021-08-25 14:43 dpdklab
2021-08-25 14:30 dpdklab
2021-08-25 14:20 dpdklab
2021-08-25 14:19 dpdklab
2021-08-25 14:19 dpdklab
2021-08-25 14:08 dpdklab
2021-08-25 14:05 dpdklab
2021-08-25 13:56 dpdklab
2021-08-25 13:52 dpdklab
2021-08-25 13:51 dpdklab
2021-08-25 13:49 dpdklab
2021-08-25 13:47 dpdklab
2021-08-25 13:34 dpdklab
2021-08-25 13:33 dpdklab
2021-08-25 13:28 dpdklab
2021-08-25 13:21 dpdklab
2021-08-25 13:17 dpdklab
2021-08-25 13:16 dpdklab
2021-08-25 13:08 dpdklab
2021-08-25 13:04 dpdklab
2021-08-25 13:01 dpdklab
2021-08-25 13:01 dpdklab
2021-08-25 12:46 dpdklab
[not found] <20210825112700.83810-1-xuan.ding@intel.com>
2021-08-25 11:37 ` 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=20210825145941.844E189060@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.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).