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| pw151136 [PATCH] [v5] net: add thread-safe crc api
Date: Fri, 07 Feb 2025 16:17:56 -0800 (PST) [thread overview]
Message-ID: <67a6a2b4.050a0220.3083cd.c051SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250207182443.9775-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/151136
_Performance Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Friday, February 07 2025 18:24:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7125636162d67b1c40ba6802a3ff4466d125d243
151136 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#211586
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | 1.7% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32530/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-02-08 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250207182443.9775-1-arkadiuszx.kusztal@intel.com>
2025-02-07 17:51 ` |SUCCESS| pw151136 [PATCH v5] " qemudev
2025-02-07 17:55 ` qemudev
2025-02-07 18:25 ` |WARNING| " checkpatch
2025-02-07 20:25 ` |SUCCESS| " 0-day Robot
2025-02-08 0:11 ` |SUCCESS| pw151136 [PATCH] [v5] " dpdklab
2025-02-08 0:17 ` dpdklab [this message]
2025-02-08 0:37 ` dpdklab
2025-02-08 0:46 ` dpdklab
2025-02-08 1:45 ` dpdklab
2025-02-08 1:56 ` |PENDING| " dpdklab
2025-02-08 2:24 ` dpdklab
2025-02-08 2:29 ` |SUCCESS| " dpdklab
2025-02-08 2:57 ` dpdklab
2025-02-08 3:00 ` |PENDING| " 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=67a6a2b4.050a0220.3083cd.c051SMTPIN_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).