From: Kevin Traynor <ktraynor@redhat.com>
To: YangHang Liu <yanghliu@redhat.com>
Cc: stable@dpdk.org, Luca Boccassi <bluca@debian.org>,
Pei Zhang <pezhang@redhat.com>
Subject: Re: 21.11.6 patches review and test
Date: Tue, 9 Jan 2024 09:43:21 +0000 [thread overview]
Message-ID: <13a56a5a-79ad-4cdd-88a5-9363bf2add16@redhat.com> (raw)
In-Reply-To: <CAGYh1E_Egn2xLiaYx=dqzT=iNxhjQPWcCTOh9JP7Kmky1AAj8Q@mail.gmail.com>
On 28/12/2023 03:06, YangHang Liu wrote:
> 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 4Q 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 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
> # git describe
> v21.11.6-rc1
>
> Test device : X540-AT2 NIC(ixgbe, 10G)
>
> On Wed, Dec 20, 2023 at 9:22 PM Kevin Traynor <ktraynor@redhat.com
> <mailto:ktraynor@redhat.com>> wrote:
>
> Hi all,
>
> Here is a list of patches targeted for stable release 21.11.6.
>
> The planned date for the final release is 12 January.
>
> Please help with testing and validation of your use cases and report
> any issues/results with reply-all to this mail. For the final release
> the fixes and reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
> https://dpdk.org/browse/dpdk-stable/tag/?id=v21.11.6-rc1
> <https://dpdk.org/browse/dpdk-stable/tag/?id=v21.11.6-rc1>
>
> These patches are located at branch 21.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
> <https://dpdk.org/browse/dpdk-stable/>
>
> Thanks.
>
> Kevin
Thanks YangHang. I will add to the validation notes,
Kevin.
next prev parent reply other threads:[~2024-01-09 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 13:22 Kevin Traynor
2023-12-28 3:06 ` YangHang Liu
2024-01-09 9:43 ` Kevin Traynor [this message]
2024-01-03 14:43 ` Ali Alnubani
2024-01-09 9:41 ` Kevin Traynor
2024-01-09 9:48 ` Kevin Traynor
2024-01-10 1:28 ` Xu, HailinX
2024-01-10 9:46 ` Kevin Traynor
2024-01-15 7:50 ` Xu, HailinX
2024-01-15 10:25 ` Kevin Traynor
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=13a56a5a-79ad-4cdd-88a5-9363bf2add16@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=pezhang@redhat.com \
--cc=stable@dpdk.org \
--cc=yanghliu@redhat.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).