From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124797 [PATCH] lib/bpf: Rename 'bpf_validate' to avoid potential conflict with libpcap
Date: Fri, 3 Mar 2023 17:29:55 +0000 (UTC) [thread overview]
Message-ID: <20230303172955.93843600AF@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124797
_Performance Testing PASS_
Submitter: Martzki <mars14850@gmail.com>
Date: Friday, March 03 2023 13:56:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124797 --> performance testing pass
Test environment and result as below:
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/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25609/
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-03 17:29 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 17:29 dpdklab [this message]
[not found] <20230303135655.78749-1-mars14850@gmail.com>
2023-03-03 15:59 ` 0-day Robot
2023-03-06 7:05 ` qemudev
2023-03-06 7:05 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-03-05 7:39 dpdklab
2023-03-05 7:39 dpdklab
2023-03-05 7:38 dpdklab
2023-03-05 7:31 dpdklab
2023-03-05 7:21 dpdklab
2023-03-05 7:19 dpdklab
2023-03-05 7:16 dpdklab
2023-03-05 7:15 dpdklab
2023-03-05 7:12 dpdklab
2023-03-05 7:07 dpdklab
2023-03-05 7:06 dpdklab
2023-03-05 7:05 dpdklab
2023-03-05 7:02 dpdklab
2023-03-05 6:57 dpdklab
2023-03-05 6:56 dpdklab
2023-03-05 6:54 dpdklab
2023-03-05 6:52 dpdklab
2023-03-05 6:45 dpdklab
2023-03-05 6:44 dpdklab
2023-03-05 6:43 dpdklab
2023-03-05 6:36 dpdklab
2023-03-05 6:31 dpdklab
2023-03-05 6:26 dpdklab
2023-03-05 6:21 dpdklab
2023-03-05 6:16 dpdklab
2023-03-05 6:10 dpdklab
2023-03-05 6:08 dpdklab
2023-03-04 8:43 dpdklab
2023-03-04 8:05 dpdklab
2023-03-04 7:38 dpdklab
2023-03-04 7:31 dpdklab
2023-03-04 1:34 dpdklab
2023-03-04 1:24 dpdklab
2023-03-03 18:44 dpdklab
2023-03-03 18:07 dpdklab
2023-03-03 17:48 dpdklab
2023-03-03 17:43 dpdklab
2023-03-03 17:39 dpdklab
2023-03-03 17:36 dpdklab
2023-03-03 17:35 dpdklab
2023-03-03 17:34 dpdklab
2023-03-03 17:31 dpdklab
2023-03-03 17:30 dpdklab
2023-03-03 17:28 dpdklab
2023-03-03 17:27 dpdklab
2023-03-03 17:26 dpdklab
2023-03-03 17:01 dpdklab
2023-03-03 16:57 dpdklab
2023-03-03 16:49 dpdklab
2023-03-03 16:48 dpdklab
2023-03-03 16:47 dpdklab
2023-03-03 16:46 dpdklab
2023-03-03 16:44 dpdklab
2023-03-03 16:43 dpdklab
2023-03-03 16:43 dpdklab
2023-03-03 16:40 dpdklab
2023-03-03 16:37 dpdklab
2023-03-03 16:30 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=20230303172955.93843600AF@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@dpdk.org \
--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).