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
Subject: |SUCCESS| pw140186-140187 [PATCH] [2/2] net/virtio: fix fortify memc
Date: Mon, 20 May 2024 18:50:23 -0700 (PDT)	[thread overview]
Message-ID: <664bfddf.d40a0220.bfad.f065SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240521010105.81868-2-stephen@networkplumber.org>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/140187

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, May 21 2024 01:01:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140186-140187 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-21  1:50 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240521010105.81868-2-stephen@networkplumber.org>
2024-05-21  0:35 ` |SUCCESS| pw140186-140187 [PATCH 2/2] net/virtio: fix fortify memcpy warning qemudev
2024-05-21  0:39 ` qemudev
2024-05-21  1:02 ` |SUCCESS| pw140187 " checkpatch
2024-05-21  1:48 ` |SUCCESS| pw140186-140187 [PATCH] [2/2] net/virtio: fix fortify memc dpdklab
2024-05-21  1:48 ` dpdklab
2024-05-21  1:48 ` dpdklab
2024-05-21  1:49 ` dpdklab
2024-05-21  1:49 ` dpdklab
2024-05-21  1:50 ` dpdklab
2024-05-21  1:50 ` dpdklab
2024-05-21  1:50 ` dpdklab [this message]
2024-05-21  1:50 ` dpdklab
2024-05-21  1:50 ` dpdklab
2024-05-21  1:51 ` dpdklab
2024-05-21  1:51 ` dpdklab
2024-05-21  1:51 ` dpdklab
2024-05-21  1:51 ` dpdklab
2024-05-21  1:52 ` dpdklab
2024-05-21  1:52 ` dpdklab
2024-05-21  1:52 ` dpdklab
2024-05-21  1:53 ` dpdklab
2024-05-21  1:53 ` dpdklab
2024-05-21  1:53 ` dpdklab
2024-05-21  1:53 ` dpdklab
2024-05-21  1:53 ` dpdklab
2024-05-21  1:54 ` dpdklab
2024-05-21  1:54 ` dpdklab
2024-05-21  1:55 ` dpdklab
2024-05-21  1:55 ` dpdklab
2024-05-21  1:55 ` dpdklab
2024-05-21  1:55 ` dpdklab
2024-05-21  1:56 ` dpdklab
2024-05-21  1:56 ` dpdklab
2024-05-21  1:56 ` dpdklab
2024-05-21  1:57 ` dpdklab
2024-05-21  1:57 ` dpdklab
2024-05-21  1:57 ` dpdklab
2024-05-21  1:57 ` dpdklab
2024-05-21  1:58 ` dpdklab
2024-05-21  1:58 ` dpdklab
2024-05-21  1:58 ` dpdklab
2024-05-21  1:58 ` dpdklab
2024-05-21  1:58 ` dpdklab
2024-05-21  2:01 ` dpdklab
2024-05-21  2:01 ` dpdklab
2024-05-21  2:03 ` dpdklab
2024-05-21  2:03 ` |SUCCESS| pw140187 [PATCH 2/2] net/virtio: fix fortify memcpy warning 0-day Robot
2024-05-21  2:05 ` |SUCCESS| pw140186-140187 [PATCH] [2/2] net/virtio: fix fortify memc dpdklab
2024-05-21  2:06 ` |FAILURE| " dpdklab
2024-05-21  2:06 ` |SUCCESS| " dpdklab
2024-05-21  2:07 ` dpdklab
2024-05-21  2:07 ` dpdklab
2024-05-21  2:08 ` dpdklab
2024-05-21  2:12 ` dpdklab
2024-05-21  2:13 ` dpdklab
2024-05-21  2:14 ` dpdklab
2024-05-21  2:14 ` |FAILURE| " dpdklab
2024-05-21  2:14 ` |SUCCESS| " dpdklab
2024-05-21  2:14 ` |FAILURE| " dpdklab
2024-05-21  2:15 ` dpdklab
2024-05-21  2:15 ` dpdklab
2024-05-21  2:15 ` dpdklab
2024-05-21  2:16 ` dpdklab
2024-05-21  2:17 ` |SUCCESS| " dpdklab
2024-05-21  2:17 ` |FAILURE| " dpdklab
2024-05-21  2:20 ` |SUCCESS| " dpdklab
2024-05-21  2:20 ` dpdklab
2024-05-21  2:21 ` dpdklab
2024-05-21  2:21 ` dpdklab
2024-05-21  2:23 ` dpdklab
2024-05-21  2:24 ` |FAILURE| " dpdklab
2024-05-21  2:24 ` |SUCCESS| " dpdklab
2024-05-21  2:24 ` dpdklab
2024-05-21  2:26 ` dpdklab
2024-05-21  2:28 ` dpdklab
2024-05-21  2:30 ` dpdklab
2024-05-21  2:32 ` dpdklab
2024-05-21  2:33 ` dpdklab
2024-05-21  2:34 ` dpdklab
2024-05-21  2:34 ` dpdklab
2024-05-21  2:35 ` dpdklab
2024-05-21  2:36 ` dpdklab
2024-05-21  2:37 ` dpdklab
2024-05-21  2:41 ` dpdklab
2024-05-21  2:42 ` dpdklab
2024-05-21  2:43 ` dpdklab
2024-05-21  2:45 ` dpdklab
2024-05-21  2:49 ` dpdklab
2024-05-21  3:03 ` dpdklab
2024-05-21  3:04 ` dpdklab
2024-05-23  5:56 ` dpdklab
2024-05-23  6:15 ` 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=664bfddf.d40a0220.bfad.f065SMTPIN_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).