From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136868 [PATCH] net/gve: Change ERR to DEBUG to prevent f
Date: Sun, 18 Feb 2024 19:22:31 -0800 (PST) [thread overview]
Message-ID: <65d2c977.050a0220.3c924.5e64SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136868
_Performance Testing PASS_
Submitter: Rushil Gupta <rushilg@google.com>
Date: Monday, February 19 2024 02:44:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d9d436f263a3f4313ad4c029a9905d6be6cbd6
136868 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29178/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-19 3:22 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 3:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-19 4:46 dpdklab
2024-02-19 4:23 dpdklab
2024-02-19 4:18 dpdklab
2024-02-19 4:15 dpdklab
2024-02-19 4:02 dpdklab
2024-02-19 3:58 dpdklab
2024-02-19 3:57 dpdklab
2024-02-19 3:54 dpdklab
2024-02-19 3:53 dpdklab
2024-02-19 3:52 dpdklab
2024-02-19 3:51 dpdklab
2024-02-19 3:50 dpdklab
2024-02-19 3:50 dpdklab
2024-02-19 3:49 dpdklab
2024-02-19 3:47 dpdklab
2024-02-19 3:46 dpdklab
2024-02-19 3:45 dpdklab
2024-02-19 3:43 dpdklab
2024-02-19 3:42 dpdklab
2024-02-19 3:41 dpdklab
2024-02-19 3:41 dpdklab
2024-02-19 3:40 dpdklab
2024-02-19 3:40 dpdklab
2024-02-19 3:39 dpdklab
2024-02-19 3:39 dpdklab
2024-02-19 3:38 dpdklab
2024-02-19 3:37 dpdklab
2024-02-19 3:37 dpdklab
2024-02-19 3:37 dpdklab
2024-02-19 3:36 dpdklab
2024-02-19 3:35 dpdklab
2024-02-19 3:35 dpdklab
2024-02-19 3:35 dpdklab
2024-02-19 3:35 dpdklab
2024-02-19 3:34 dpdklab
2024-02-19 3:33 dpdklab
2024-02-19 3:32 dpdklab
2024-02-19 3:32 dpdklab
2024-02-19 3:31 dpdklab
2024-02-19 3:31 dpdklab
2024-02-19 3:31 dpdklab
2024-02-19 3:30 dpdklab
2024-02-19 3:30 dpdklab
2024-02-19 3:30 dpdklab
2024-02-19 3:29 dpdklab
2024-02-19 3:28 dpdklab
2024-02-19 3:28 dpdklab
2024-02-19 3:28 dpdklab
2024-02-19 3:27 dpdklab
2024-02-19 3:27 dpdklab
2024-02-19 3:26 dpdklab
2024-02-19 3:26 dpdklab
2024-02-19 3:25 dpdklab
2024-02-19 3:25 dpdklab
2024-02-19 3:25 dpdklab
2024-02-19 3:24 dpdklab
2024-02-19 3:24 dpdklab
2024-02-19 3:23 dpdklab
2024-02-19 3:23 dpdklab
2024-02-19 3:23 dpdklab
2024-02-19 3:22 dpdklab
2024-02-19 3:22 dpdklab
2024-02-19 3:21 dpdklab
2024-02-19 3:21 dpdklab
2024-02-19 3:21 dpdklab
2024-02-19 3:21 dpdklab
2024-02-19 3:20 dpdklab
2024-02-19 3:20 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=65d2c977.050a0220.3c924.5e64SMTPIN_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).