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| pw121820-121821 [PATCH] [v2, 2/2] ethdev: add quota flow action and item
Date: Wed, 11 Jan 2023 10:01:39 +0000 (UTC)	[thread overview]
Message-ID: <20230111100140.2160C60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, January 11 2023 09:22:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fe2c18a0a8b22703dec3add385a371ad819d7872

121820-121821 --> 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         | -2.9%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 2.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 1.6%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-01-11 10:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-11 16:31 dpdklab
2023-01-11 16:27 dpdklab
2023-01-11 15:51 dpdklab
2023-01-11 14:57 dpdklab
2023-01-11 14:57 dpdklab
2023-01-11 14:57 dpdklab
2023-01-11 14:57 dpdklab
2023-01-11 14:56 dpdklab
2023-01-11 14:53 dpdklab
2023-01-11 14:52 dpdklab
2023-01-11 14:51 dpdklab
2023-01-11 14:25 dpdklab
2023-01-11 14:25 dpdklab
2023-01-11 14:20 dpdklab
2023-01-11 11:31 dpdklab
2023-01-11 10:34 dpdklab
2023-01-11 10:14 dpdklab
2023-01-11 10:08 dpdklab
2023-01-11  9:58 dpdklab
2023-01-11  9:57 dpdklab
2023-01-11  9:54 dpdklab
     [not found] <20230111092250.30880-2-getelson@nvidia.com>
2023-01-11  9:16 ` |SUCCESS| pw121820-121821 [PATCH v2 " qemudev
2023-01-11  9:20 ` 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=20230111100140.2160C60092@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).