From: YangHang Liu <yanghliu@redhat.com>
To: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
stable@dpdk.org
Cc: Chao Yang <chayang@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
David Marchand <david.marchand@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>,
luca.boccassi@gmail.com
Subject: RedHat QE's test result against DPDK stable 20.11.10-rc1
Date: Sat, 9 Dec 2023 11:28:41 +0800 [thread overview]
Message-ID: <CAGYh1E_JvA0dZ1iiO=2MR-va7hzB34jA7GXScaYmBQ+GjHHGtA@mail.gmail.com> (raw)
I tested below 18 scenarios on RHEL9 and didn't find any new dpdk issues.
Guest with device assignment(PF) throughput testing(1G hugepage size): PASS
Guest with device assignment(PF) throughput testing(2M hugepage size) : PASS
Guest with device assignment(VF) throughput testing: PASS
PVP (host dpdk testpmd as vswitch) 1Q: throughput testing: PASS
PVP vhost-user 2Q throughput testing: PASS
PVP vhost-user 1Q - cross numa node throughput testing: PASS
Guest with vhost-user 2 queues throughput testing: PASS
vhost-user reconnect with dpdk-client, qemu-server qemu reconnect: PASS
vhost-user reconnect with dpdk-client, qemu-server ovs reconnect: PASS
PVP reconnect with dpdk-client, qemu-server: PASS
PVP 1Q live migration testing: PASS
PVP 1Q cross numa node live migration testing: PASS
Guest with ovs+dpdk+vhost-user 1Q live migration testing: PASS
Guest with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
Guest with ovs+dpdk+vhost-user 4Q live migration testing: PASS
Host PF + DPDK testing: PASS
Host VF + DPDK testing: PASS
Test Versions: qemu-kvm-7.2.0 + kernel 5.14 + libvirt-9.0.0
# git log
commit a98b988ea5301b4218de5a558d84dbf5dcde9a05
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Dec 1 11:45:44 2023 +0000
version: 20.11.10-rc1
Signed-off-by: Luca Boccassi <bluca@debian.org>
Test device : X540-AT2 NIC(ixgbe, 10G)
Best Regards,
YangHang Liu
reply other threads:[~2023-12-09 3:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGYh1E_JvA0dZ1iiO=2MR-va7hzB34jA7GXScaYmBQ+GjHHGtA@mail.gmail.com' \
--to=yanghliu@redhat.com \
--cc=chayang@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).