From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137808 [PATCH v7] mempool: test performance with larger bursts
Date: Sun, 3 Mar 2024 03:40:52 +0800 [thread overview]
Message-ID: <202403021940.422Jeqp1066445@localhost.localdomain> (raw)
In-Reply-To: <20240302200408.6419-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137808
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Sat, 2 Mar 2024 21:04:08 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364
137808 --> 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-02 20:05 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240302200408.6419-1-mb@smartsharesystems.com>
2024-03-02 19:40 ` qemudev [this message]
2024-03-02 19:45 ` qemudev
2024-03-02 20:04 ` checkpatch
2024-03-02 20:43 ` |SUCCESS| pw137808 [PATCH] [v7] mempool: test performance with large dpdklab
2024-03-02 20:44 ` dpdklab
2024-03-02 20:45 ` dpdklab
2024-03-02 20:45 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:48 ` dpdklab
2024-03-02 20:48 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:50 ` dpdklab
2024-03-02 20:50 ` dpdklab
2024-03-02 20:51 ` dpdklab
2024-03-02 20:51 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:54 ` dpdklab
2024-03-02 20:54 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:57 ` dpdklab
2024-03-02 20:57 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:03 ` dpdklab
2024-03-02 21:04 ` dpdklab
2024-03-02 21:05 ` |SUCCESS| pw137808 [PATCH v7] mempool: test performance with larger bursts 0-day Robot
2024-03-02 21:22 ` |SUCCESS| pw137808 [PATCH] [v7] mempool: test performance with large dpdklab
2024-03-02 21:53 ` dpdklab
2024-03-02 22:00 ` dpdklab
2024-03-02 22:13 ` dpdklab
2024-03-03 6:21 ` dpdklab
2024-03-06 16:15 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 17:05 ` 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=202403021940.422Jeqp1066445@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).