From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio Tx packed path
Date: Fri, 29 Mar 2024 07:13:01 +0800 [thread overview]
Message-ID: <202403282313.42SND1ix145181@localhost.localdomain> (raw)
In-Reply-To: <20240328233338.56544-1-rdna@apple.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138965
_Compilation OK_
Submitter: Andrey Ignatov <rdna@apple.com>
Date: Thu, 28 Mar 2024 16:33:38 -0700
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: deedfb86a7a6e10064d3cccd593f62072de96e36
138965 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-03-28 23:38 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240328233338.56544-1-rdna@apple.com>
2024-03-28 23:13 ` qemudev [this message]
2024-03-28 23:17 ` qemudev
2024-03-29 0:17 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio dpdklab
2024-03-29 0:18 ` dpdklab
2024-03-29 0:18 ` dpdklab
2024-03-29 0:18 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:19 ` dpdklab
2024-03-29 0:20 ` dpdklab
2024-03-29 0:20 ` dpdklab
2024-03-29 0:23 ` dpdklab
2024-03-29 0:23 ` dpdklab
2024-03-29 0:24 ` dpdklab
2024-03-29 0:25 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio Tx packed path 0-day Robot
2024-03-29 0:25 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio dpdklab
2024-03-29 0:25 ` dpdklab
2024-03-29 0:25 ` dpdklab
2024-03-29 0:26 ` dpdklab
2024-03-29 0:27 ` dpdklab
2024-03-29 0:27 ` dpdklab
2024-03-29 0:27 ` dpdklab
2024-03-29 0:35 ` |FAILURE| " dpdklab
2024-03-29 0:35 ` |SUCCESS| " dpdklab
2024-03-29 0:35 ` dpdklab
2024-03-29 0:35 ` dpdklab
2024-03-29 0:36 ` dpdklab
2024-03-29 0:36 ` dpdklab
2024-03-29 0:36 ` dpdklab
2024-03-29 0:37 ` dpdklab
2024-03-29 0:44 ` dpdklab
2024-03-29 0:45 ` dpdklab
2024-03-29 0:45 ` dpdklab
2024-03-29 0:47 ` dpdklab
2024-03-29 0:48 ` dpdklab
2024-03-29 0:50 ` |FAILURE| " dpdklab
2024-03-29 0:50 ` |SUCCESS| " dpdklab
2024-03-29 0:51 ` dpdklab
2024-03-29 0:53 ` dpdklab
2024-03-29 0:54 ` dpdklab
2024-03-29 0:54 ` dpdklab
2024-03-29 0:55 ` dpdklab
2024-03-29 0:55 ` dpdklab
2024-03-29 0:56 ` dpdklab
2024-03-29 0:57 ` dpdklab
2024-03-29 0:57 ` dpdklab
2024-03-29 0:59 ` dpdklab
2024-03-29 1:03 ` dpdklab
2024-03-29 1:07 ` dpdklab
2024-03-29 1:10 ` dpdklab
2024-03-29 1:11 ` dpdklab
2024-03-29 1:12 ` |FAILURE| " dpdklab
2024-03-29 1:12 ` dpdklab
2024-03-29 1:13 ` |SUCCESS| " dpdklab
2024-03-29 1:13 ` dpdklab
2024-03-29 1:14 ` dpdklab
2024-03-29 1:17 ` dpdklab
2024-03-29 1:17 ` dpdklab
2024-03-29 1:19 ` dpdklab
2024-03-29 1:21 ` |FAILURE| " dpdklab
2024-03-29 1:24 ` dpdklab
2024-03-29 1:25 ` dpdklab
2024-03-29 1:29 ` dpdklab
2024-03-29 1:29 ` |SUCCESS| " dpdklab
2024-03-29 1:33 ` dpdklab
2024-03-29 1:39 ` |FAILURE| " dpdklab
2024-03-29 1:40 ` dpdklab
2024-03-29 1:42 ` dpdklab
2024-03-29 1:44 ` |SUCCESS| " dpdklab
2024-03-29 1:49 ` dpdklab
2024-03-29 1:51 ` |FAILURE| " dpdklab
2024-03-29 1:54 ` dpdklab
2024-03-29 1:55 ` dpdklab
2024-03-29 1:56 ` dpdklab
2024-03-29 2:00 ` |SUCCESS| " dpdklab
2024-03-29 2:05 ` dpdklab
2024-03-29 2:09 ` dpdklab
2024-03-29 2:12 ` dpdklab
2024-03-29 2:22 ` dpdklab
2024-03-29 3:06 ` dpdklab
2024-03-29 3:56 ` dpdklab
2024-04-02 18:25 ` dpdklab
2024-04-02 18:32 ` dpdklab
2024-04-02 18:37 ` dpdklab
2024-04-02 18:42 ` dpdklab
2024-04-02 19:02 ` dpdklab
2024-03-28 23:37 |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio Tx packed path checkpatch
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=202403282313.42SND1ix145181@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).