From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136223 [PATCH] ethdev: fast path async flow API
Date: Tue, 30 Jan 2024 13:52:14 -0800 (PST) [thread overview]
Message-ID: <65b96f8e.170a0220.d3412.9c02SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136223
_Performance Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, January 30 2024 18:17:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136223 --> 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 | 0.3% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -1.5% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 4.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 3.9% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28994/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-30 21:52 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 21:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 23:12 dpdklab
2024-01-30 23:01 dpdklab
2024-01-30 22:51 dpdklab
2024-01-30 22:47 dpdklab
2024-01-30 22:37 dpdklab
2024-01-30 22:36 dpdklab
2024-01-30 22:35 dpdklab
2024-01-30 22:34 dpdklab
2024-01-30 22:34 dpdklab
2024-01-30 22:33 dpdklab
2024-01-30 22:33 dpdklab
2024-01-30 22:31 dpdklab
2024-01-30 22:31 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:20 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:13 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:11 dpdklab
2024-01-30 22:09 dpdklab
2024-01-30 22:05 dpdklab
2024-01-30 22:04 dpdklab
2024-01-30 22:04 dpdklab
2024-01-30 22:03 dpdklab
2024-01-30 22:02 dpdklab
2024-01-30 22:01 dpdklab
2024-01-30 22:01 dpdklab
2024-01-30 21:59 dpdklab
2024-01-30 21:59 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:56 dpdklab
2024-01-30 21:55 dpdklab
2024-01-30 21:55 dpdklab
2024-01-30 21:54 dpdklab
2024-01-30 21:53 dpdklab
2024-01-30 21:52 dpdklab
2024-01-30 21:52 dpdklab
2024-01-30 21:51 dpdklab
2024-01-30 21:50 dpdklab
2024-01-30 21:49 dpdklab
2024-01-30 21:48 dpdklab
2024-01-30 21:47 dpdklab
2024-01-30 21:47 dpdklab
2024-01-30 21:47 dpdklab
[not found] <20240130181751.1425388-1-dsosnowski@nvidia.com>
2024-01-30 17:56 ` qemudev
2024-01-30 18:00 ` qemudev
2024-01-30 18:19 ` checkpatch
2024-01-30 19:23 ` 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=65b96f8e.170a0220.d3412.9c02SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).