From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw72419-72421 [PATCH] [v3, 1/3] vdpa/mlx5: optimize notification events
Date: Mon, 29 Jun 2020 10:56:09 -0400 (EDT) [thread overview]
Message-ID: <20200629145609.934D26D437@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/72419
_Performance Testing PASS_
Submitter: Matan Azrad <matan@mellanox.com>
Date: Monday, June 29 2020 14:01:54
DPDK git baseline: Repo:dpdk-next-virtio
Branch: master
CommitID:4a756a8c2f9dbf1f43e2638028931331e2a617eb
72419-72421 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 512 | 0.044 |
+------------+---------+-------------------------------------+
| 64 | 2048 | -0.005 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11720/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-06-29 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:56 dpdklab [this message]
2020-06-29 15:32 dpdklab
2020-06-29 15:43 dpdklab
2020-06-29 17:54 dpdklab
2020-06-29 18:08 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=20200629145609.934D26D437@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.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).