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| pw125374-125407 [PATCH] [33/33] doc: update virtio guide
Date: Wed, 22 Mar 2023 01:44:24 +0000 (UTC) [thread overview]
Message-ID: <20230322014424.5AA9760216@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125407
_Performance Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Tuesday, March 21 2023 23:59:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1a80f6062cf74e4b689b8b9a4f905a24efec527a
125374-125407 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25822/
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-22 1:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 1:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-24 9:10 dpdklab
2023-03-24 7:11 dpdklab
2023-03-23 8:47 dpdklab
2023-03-23 8:27 dpdklab
2023-03-23 3:37 dpdklab
2023-03-23 2:42 dpdklab
2023-03-22 18:59 dpdklab
2023-03-22 18:59 dpdklab
2023-03-22 3:58 dpdklab
2023-03-22 3:36 dpdklab
2023-03-22 3:10 dpdklab
2023-03-22 3:06 dpdklab
2023-03-22 3:02 dpdklab
2023-03-22 2:57 dpdklab
2023-03-22 2:57 dpdklab
2023-03-22 2:56 dpdklab
2023-03-22 2:52 dpdklab
2023-03-22 2:51 dpdklab
2023-03-22 2:49 dpdklab
2023-03-22 2:49 dpdklab
2023-03-22 2:47 dpdklab
2023-03-22 2:45 dpdklab
2023-03-22 2:03 dpdklab
2023-03-22 1:53 dpdklab
2023-03-22 1:50 dpdklab
2023-03-22 1:50 dpdklab
2023-03-22 1:48 dpdklab
2023-03-22 1:47 dpdklab
2023-03-22 1:44 dpdklab
2023-03-22 1:42 dpdklab
2023-03-22 1:41 dpdklab
2023-03-22 1:35 dpdklab
[not found] <20230321235941.2169068-34-ferruh.yigit@amd.com>
2023-03-22 0:12 ` |SUCCESS| pw125374-125407 [PATCH 33/33] " qemudev
2023-03-22 0:16 ` qemudev
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=20230322014424.5AA9760216@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).