From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw102903 [PATCH] test: fix forwarding packets through not-ready port
Date: Tue, 26 Oct 2021 20:45:31 +0000 (UTC) [thread overview]
Message-ID: <20211026204531.409BF6008E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3238 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/102903
_Performance Testing PASS_
Submitter: Ananyev, Konstantin <konstantin.ananyev@intel.com>
Date: Tuesday, October 26 2021 11:19:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
102903 --> 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 25000 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% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19726/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-26 20:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 20:38 dpdklab
2021-10-27 7:00 dpdklab
2021-10-27 6:48 dpdklab
2021-10-27 6:24 dpdklab
2021-10-27 6:11 dpdklab
2021-10-27 6:06 dpdklab
2021-10-26 21:27 dpdklab
2021-10-26 21:14 dpdklab
2021-10-26 21:00 dpdklab
2021-10-26 20:31 dpdklab
2021-10-26 16:14 dpdklab
2021-10-26 15:57 dpdklab
2021-10-26 15:09 dpdklab
2021-10-26 14:51 dpdklab
2021-10-26 14:47 dpdklab
2021-10-26 14:45 dpdklab
2021-10-26 14:42 dpdklab
2021-10-26 14:34 dpdklab
2021-10-26 14:28 dpdklab
2021-10-26 14:25 dpdklab
2021-10-26 14:21 dpdklab
2021-10-26 14:20 dpdklab
2021-10-26 14:14 dpdklab
2021-10-26 14:01 dpdklab
[not found] <20211026111943.19957-1-konstantin.ananyev@intel.com>
2021-10-26 11:21 ` 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=20211026204531.409BF6008E@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=dpdk-test-reports@dpdk.org \
--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).