From: Kevin Traynor <ktraynor@redhat.com>
To: Yanghang Liu <yanghliu@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: 21.11.9 patches review and test
Date: Wed, 11 Dec 2024 16:28:17 +0000 [thread overview]
Message-ID: <0105a7a3-3cd9-450e-89b8-09d72cfaf63a@redhat.com> (raw)
In-Reply-To: <CAGYh1E82gm_taYJgV5EXt-eF0Y5yHZGvDAb5cvhT2LN9d+Fi+A@mail.gmail.com>
On 09/12/2024 03:44, Yanghang Liu wrote:
> I tested below 18 scenarios on RHEL 9.2 and didn't find any new dpdk issues.
>
Thanks Yanghang. I will add a note about the validation to the release
notes.
Kevin.
> - 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
> - kernel 5.14
> - libvirt 9.0
> - git describe
> - v21.11.9-rc1
> - git log
>
> commit f197f1e13ccfb74c92ad05602443dd0984f39540
>
> Author: Kevin Traynor <ktraynor@redhat.com>
>
> Date: Wed Dec 4 15:24:08 2024 +0000
>
> version: 21.11.9-rc1
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>
>
> - Test device : X540-AT2 NIC(ixgbe, 10G)
>
> Tested-by: Yanghang Liu <yanghliu@redhat.com>
>
>
> On Wed, Dec 4, 2024 at 11:58 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.9.
>>
>> The planned date for the final release is 17th December 2024.
>>
>> 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.9-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
next prev parent reply other threads:[~2024-12-11 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:58 21.11.9 patches review and test Kevin Traynor
2024-12-09 3:44 ` Yanghang Liu
2024-12-11 16:28 ` Kevin Traynor [this message]
2024-12-16 18:14 ` Ali Alnubani
2024-12-17 12:54 ` Kevin Traynor
2024-12-17 10:01 ` Xu, HailinX
2024-12-17 11:30 ` Kevin Traynor
2024-12-17 17:48 ` Kevin Traynor
2024-12-18 2:46 ` Xu, HailinX
2024-12-23 2:48 ` Xu, HailinX
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=0105a7a3-3cd9-450e-89b8-09d72cfaf63a@redhat.com \
--to=ktraynor@redhat.com \
--cc=dev@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).