automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw120987-120988 [PATCH] [v2, 2/2] test: enable lcores test on Windows
Date: Fri, 16 Dec 2022 17:48:48 +0000 (UTC)	[thread overview]
Message-ID: <20221216174848.13BF9600DC@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/120988

_Performance Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, December 16 2022 17:16:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79

120987-120988 --> 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.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.3%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.4%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -2.4%                        |
+----------+-------------+---------+------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24756/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2022-12-16 17:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 17:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-16 19:06 dpdklab
2022-12-16 19:06 dpdklab
2022-12-16 19:04 dpdklab
2022-12-16 19:03 dpdklab
2022-12-16 18:56 dpdklab
2022-12-16 18:42 dpdklab
2022-12-16 18:29 dpdklab
2022-12-16 18:28 dpdklab
2022-12-16 18:25 dpdklab
2022-12-16 18:23 dpdklab
2022-12-16 18:21 dpdklab
2022-12-16 18:21 dpdklab
2022-12-16 18:16 dpdklab
2022-12-16 18:09 dpdklab
2022-12-16 18:03 dpdklab
2022-12-16 18:00 dpdklab
2022-12-16 17:56 dpdklab
2022-12-16 17:52 dpdklab
2022-12-16 17:46 dpdklab
2022-12-16 17:44 dpdklab
2022-12-16 17:40 dpdklab
     [not found] <1671211000-14856-3-git-send-email-roretzla@linux.microsoft.com>
2022-12-16 17:08 ` |SUCCESS| pw120987-120988 [PATCH v2 " qemudev
2022-12-16 17:12 ` 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=20221216174848.13BF9600DC@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).