From: YangHang Liu <yanghliu@redhat.com>
To: luca.boccassi@gmail.com
Cc: stable@dpdk.org, dev@dpdk.org,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
benjamin.walker@intel.com,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Ian Stokes <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
qian.q.xu@intel.com, Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
yuan.peng@intel.com, zhaoyan.chen@intel.com,
Chao Yang <chayang@redhat.com>
Subject: Re: 22.11.5 patches review and test
Date: Mon, 8 Apr 2024 12:08:42 +0800 [thread overview]
Message-ID: <CAGYh1E8UbFLdFihd4UebzCjMrf2u7KNdqVQCAmnbt4gbvQVJ7Q@mail.gmail.com> (raw)
In-Reply-To: <20240403231101.979032-1-luca.boccassi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
RedHat QE tested below 18 scenarios on RHEL9.4 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-8.2.0
- kernel 5.14
- libvirt 10.0
- git log
- Test device : X540-AT2 NIC(ixgbe, 10G)
Tested-by: Yanghang Liu<yanghliu@redhat.com>
[-- Attachment #2: Type: text/html, Size: 3166 bytes --]
next prev parent reply other threads:[~2024-04-08 4:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 23:11 luca.boccassi
2024-04-08 4:08 ` YangHang Liu [this message]
2024-04-08 9:24 ` Luca Boccassi
2024-04-15 2:37 ` Xu, HailinX
2024-04-15 9:05 ` Luca Boccassi
2024-04-17 12:41 ` Ali Alnubani
2024-04-18 14:46 ` Luca Boccassi
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=CAGYh1E8UbFLdFihd4UebzCjMrf2u7KNdqVQCAmnbt4gbvQVJ7Q@mail.gmail.com \
--to=yanghliu@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=chayang@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).