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: |SUCCESS| pw131144 [PATCH] [v2] eal: fix memory initialization deadl
Date: Mon, 04 Sep 2023 03:30:58 -0700 (PDT) [thread overview]
Message-ID: <64f5b1e2.050a0220.4497d.8c7cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/131144
_Performance Testing PASS_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Monday, September 04 2023 08:24:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131144 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27515/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-04 10:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 2:25 dpdklab
2023-09-06 2:14 dpdklab
2023-09-06 2:09 dpdklab
2023-09-06 2:04 dpdklab
2023-09-05 15:33 dpdklab
2023-09-05 15:28 dpdklab
2023-09-05 15:23 dpdklab
2023-09-05 15:23 dpdklab
2023-09-05 2:33 dpdklab
2023-09-04 13:52 dpdklab
2023-09-04 13:44 dpdklab
2023-09-04 13:22 dpdklab
2023-09-04 12:53 dpdklab
2023-09-04 12:42 dpdklab
2023-09-04 12:32 dpdklab
2023-09-04 12:15 dpdklab
2023-09-04 12:14 dpdklab
2023-09-04 12:11 dpdklab
2023-09-04 12:10 dpdklab
2023-09-04 11:58 dpdklab
2023-09-04 11:56 dpdklab
2023-09-04 11:55 dpdklab
2023-09-04 11:51 dpdklab
2023-09-04 11:48 dpdklab
2023-09-04 11:46 dpdklab
2023-09-04 11:46 dpdklab
2023-09-04 11:44 dpdklab
2023-09-04 11:35 dpdklab
2023-09-04 11:35 dpdklab
2023-09-04 11:34 dpdklab
2023-09-04 11:30 dpdklab
2023-09-04 11:29 dpdklab
2023-09-04 11:07 dpdklab
2023-09-04 11:03 dpdklab
2023-09-04 11:02 dpdklab
2023-09-04 10:43 dpdklab
2023-09-04 10:36 dpdklab
2023-09-04 10:34 dpdklab
2023-09-04 10:26 dpdklab
2023-09-04 10:19 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=64f5b1e2.050a0220.4497d.8c7cSMTPIN_ADDED_MISSING@mx.google.com \
--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).