From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125328 [PATCH] net/mlx5/hws: add check for modify-header actions
Date: Mon, 20 Mar 2023 17:54:53 +0000 (UTC) [thread overview]
Message-ID: <20230320175453.0EA2860214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125328
_Performance Testing PASS_
Submitter: Erez Shitrit <erezsh@nvidia.com>
Date: Monday, March 20 2023 16:34:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:33949800f1afcb7527b6e36c60c1548687ccb673
125328 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | -1.3% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -1.8% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 2.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 2.0% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25808/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-20 17:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 17:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-23 17:42 dpdklab
2023-03-23 17:41 dpdklab
2023-03-23 16:18 dpdklab
2023-03-23 16:18 dpdklab
2023-03-23 7:23 dpdklab
2023-03-23 6:39 dpdklab
2023-03-21 13:16 dpdklab
2023-03-21 13:02 dpdklab
2023-03-21 3:48 dpdklab
2023-03-21 2:40 dpdklab
2023-03-20 19:14 dpdklab
2023-03-20 18:58 dpdklab
2023-03-20 18:53 dpdklab
2023-03-20 18:53 dpdklab
2023-03-20 18:52 dpdklab
2023-03-20 18:48 dpdklab
2023-03-20 18:41 dpdklab
2023-03-20 18:37 dpdklab
2023-03-20 18:35 dpdklab
2023-03-20 18:32 dpdklab
2023-03-20 18:27 dpdklab
2023-03-20 18:24 dpdklab
2023-03-20 18:22 dpdklab
2023-03-20 18:19 dpdklab
2023-03-20 18:09 dpdklab
2023-03-20 18:07 dpdklab
2023-03-20 18:07 dpdklab
2023-03-20 18:07 dpdklab
2023-03-20 18:03 dpdklab
2023-03-20 18:02 dpdklab
2023-03-20 17:57 dpdklab
2023-03-20 17:54 dpdklab
2023-03-20 17:54 dpdklab
2023-03-20 17:49 dpdklab
2023-03-20 17:48 dpdklab
2023-03-20 17:42 dpdklab
2023-03-20 17:41 dpdklab
2023-03-20 17:35 dpdklab
2023-03-20 17:29 dpdklab
[not found] <20230320163443.454222-4-erezsh@nvidia.com>
2023-03-20 16:27 ` qemudev
2023-03-20 16:31 ` qemudev
2023-03-20 16:37 ` checkpatch
2023-03-20 19:59 ` 0-day Robot
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=20230320175453.0EA2860214@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).