From: YangHang Liu <yanghliu@redhat.com>
To: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Cc: Chao Yang <chayang@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
David Marchand <david.marchand@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>
Subject: RedHat QE's test result against DPDK release candidate 24.03-rc3
Date: Tue, 19 Mar 2024 10:43:25 +0800 [thread overview]
Message-ID: <CAGYh1E8EX1ZFrwVGf9WbDjRibwQN=JqLeyrUH0vKwWy2=o2L5g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
I tested below 18 scenarios on RHEL 9.2 and didn't find any new dpdk issues.
- VM with device assignment(PF) throughput testing(1G hugepage size):
PASS
- VM with device assignment(PF) throughput testing(2M hugepage size) :
PASS
- VM 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
- VM 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
- VM with ovs+dpdk+vhost-user 1Q live migration testing: PASS
- VM with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
- VM with ovs+dpdk+vhost-user 2Q live migration testing: PASS
- VM 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
- git log
commit 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Mon Mar 18 04:34:16 2024 +0100
version: 24.03-rc3
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
- Test device : X540-AT2 NIC(ixgbe, 10G)
Tested-by: Yanghang Liu<yanghliu@redhat.com>
[-- Attachment #2: Type: text/html, Size: 3601 bytes --]
reply other threads:[~2024-03-19 2:43 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='CAGYh1E8EX1ZFrwVGf9WbDjRibwQN=JqLeyrUH0vKwWy2=o2L5g@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=maxime.coquelin@redhat.com \
--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).