From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142361 [PATCH] [v1] net/e1000: do not update link status
Date: Fri, 12 Jul 2024 05:26:48 -0700 (PDT) [thread overview]
Message-ID: <66912108.050a0220.a639d.50dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1720783847-12292-1-git-send-email-junwang01@cestc.cn>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142361
_Performance Testing PASS_
Submitter: Jun Wang <junwang01@cestc.cn>
Date: Friday, July 12 2024 11:30:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:310a2131f137f62c425bdae605b8d6e9c51500dd
142361 --> 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
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30504/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-12 12:26 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1720783847-12292-1-git-send-email-junwang01@cestc.cn>
2024-07-12 11:04 ` |SUCCESS| pw142361 [PATCH v1] net/e1000: do not update link status in secondary process qemudev
2024-07-12 11:08 ` qemudev
2024-07-12 11:32 ` checkpatch
2024-07-12 12:00 ` |PENDING| pw142361 [PATCH] [v1] net/e1000: do not update link status dpdklab
2024-07-12 12:02 ` |SUCCESS| " dpdklab
2024-07-12 12:02 ` dpdklab
2024-07-12 12:05 ` |PENDING| " dpdklab
2024-07-12 12:06 ` |SUCCESS| " dpdklab
2024-07-12 12:07 ` dpdklab
2024-07-12 12:09 ` dpdklab
2024-07-12 12:10 ` dpdklab
2024-07-12 12:10 ` dpdklab
2024-07-12 12:15 ` dpdklab
2024-07-12 12:17 ` |PENDING| " dpdklab
2024-07-12 12:18 ` |SUCCESS| " dpdklab
2024-07-12 12:19 ` |PENDING| " dpdklab
2024-07-12 12:21 ` |SUCCESS| " dpdklab
2024-07-12 12:21 ` |PENDING| " dpdklab
2024-07-12 12:21 ` dpdklab
2024-07-12 12:22 ` dpdklab
2024-07-12 12:22 ` |SUCCESS| " dpdklab
2024-07-12 12:23 ` |SUCCESS| pw142361 [PATCH v1] net/e1000: do not update link status in secondary process 0-day Robot
2024-07-12 12:24 ` |PENDING| pw142361 [PATCH] [v1] net/e1000: do not update link status dpdklab
2024-07-12 12:25 ` dpdklab
2024-07-12 12:26 ` dpdklab [this message]
2024-07-12 12:27 ` dpdklab
2024-07-12 12:27 ` dpdklab
2024-07-12 12:27 ` dpdklab
2024-07-12 12:28 ` dpdklab
2024-07-12 12:28 ` dpdklab
2024-07-12 12:28 ` dpdklab
2024-07-12 12:28 ` dpdklab
2024-07-12 12:29 ` dpdklab
2024-07-12 12:30 ` dpdklab
2024-07-12 12:31 ` dpdklab
2024-07-12 12:32 ` dpdklab
2024-07-12 12:32 ` dpdklab
2024-07-12 12:32 ` dpdklab
2024-07-12 12:33 ` dpdklab
2024-07-12 12:33 ` dpdklab
2024-07-12 12:33 ` dpdklab
2024-07-12 12:33 ` dpdklab
2024-07-12 12:34 ` dpdklab
2024-07-12 12:34 ` dpdklab
2024-07-12 12:35 ` |SUCCESS| " dpdklab
2024-07-12 12:35 ` |PENDING| " dpdklab
2024-07-12 12:38 ` dpdklab
2024-07-12 12:38 ` dpdklab
2024-07-12 12:40 ` dpdklab
2024-07-12 12:40 ` dpdklab
2024-07-12 12:41 ` dpdklab
2024-07-12 12:41 ` dpdklab
2024-07-12 12:41 ` dpdklab
2024-07-12 12:42 ` dpdklab
2024-07-12 12:42 ` dpdklab
2024-07-12 12:42 ` dpdklab
2024-07-12 12:42 ` dpdklab
2024-07-12 12:43 ` dpdklab
2024-07-12 12:45 ` dpdklab
2024-07-12 12:47 ` dpdklab
2024-07-12 12:48 ` dpdklab
2024-07-12 12:49 ` dpdklab
2024-07-12 12:50 ` dpdklab
2024-07-12 12:51 ` dpdklab
2024-07-12 12:51 ` dpdklab
2024-07-12 12:52 ` |SUCCESS| " dpdklab
2024-07-12 12:56 ` |PENDING| " dpdklab
2024-07-12 12:58 ` dpdklab
2024-07-12 13:00 ` dpdklab
2024-07-12 13:05 ` dpdklab
2024-07-12 13:06 ` dpdklab
2024-07-12 13:07 ` dpdklab
2024-07-12 13:07 ` dpdklab
2024-07-12 13:07 ` dpdklab
2024-07-12 13:08 ` dpdklab
2024-07-12 13:08 ` dpdklab
2024-07-12 13:10 ` dpdklab
2024-07-12 13:10 ` dpdklab
2024-07-12 13:10 ` dpdklab
2024-07-12 13:12 ` dpdklab
2024-07-12 13:12 ` dpdklab
2024-07-12 13:13 ` dpdklab
2024-07-12 13:13 ` dpdklab
2024-07-12 13:14 ` dpdklab
2024-07-12 13:14 ` dpdklab
2024-07-12 13:19 ` dpdklab
2024-07-12 13:20 ` dpdklab
2024-07-12 13:23 ` dpdklab
2024-07-12 13:24 ` dpdklab
2024-07-12 13:26 ` |SUCCESS| " dpdklab
2024-07-12 13:28 ` |PENDING| " dpdklab
2024-07-12 13:29 ` dpdklab
2024-07-12 13:32 ` dpdklab
2024-07-12 13:34 ` dpdklab
2024-07-12 13:37 ` dpdklab
2024-07-12 13:39 ` dpdklab
2024-07-12 13:43 ` dpdklab
2024-07-12 13:43 ` dpdklab
2024-07-12 13:45 ` dpdklab
2024-07-12 13:46 ` |SUCCESS| " dpdklab
2024-07-12 13:46 ` |PENDING| " dpdklab
2024-07-12 13:47 ` dpdklab
2024-07-12 13:52 ` dpdklab
2024-07-12 13:53 ` |SUCCESS| " dpdklab
2024-07-12 13:55 ` |PENDING| " dpdklab
2024-07-12 13:58 ` dpdklab
2024-07-12 14:02 ` dpdklab
2024-07-12 14:10 ` |SUCCESS| " dpdklab
2024-07-12 14:10 ` |PENDING| " dpdklab
2024-07-12 14:13 ` dpdklab
2024-07-12 14:15 ` dpdklab
2024-07-12 14:21 ` |SUCCESS| " dpdklab
2024-07-12 21:04 ` dpdklab
2024-07-14 4:22 ` dpdklab
2024-07-14 12:09 ` dpdklab
2024-07-14 19:18 ` dpdklab
2024-07-14 19:25 ` 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=66912108.050a0220.a639d.50dfSMTPIN_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).