patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: YangHang Liu <yanghliu@redhat.com>
Cc: stable@dpdk.org
Subject: Re: 21.11.3 patches review and test
Date: Mon, 19 Dec 2022 10:39:29 +0000	[thread overview]
Message-ID: <b9472182-d6f3-46aa-9df0-5b5360a5ffd1@redhat.com> (raw)
In-Reply-To: <CAGYh1E_uDqaVPeOd_WLstfpk4pyWbyZRk7_fT8+nL9zVb0dDhg@mail.gmail.com>

On 16/12/2022 07:55, YangHang Liu wrote:
> Hi Kevin,
> 
> RedHat QE does not find new issues about the 21.11.3 dpdk during the tests.
> 

Hi YangHang. Thanks for testing and reporting these results.

Kevin.

> We tested below 17 scenarios and all got PASS on RHEL8:
> 
>     - 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 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
> 
> Versions:
> 
>     - kernel 4.18
>     - qemu-kvm-6.2
>     - DPDK
>        - commit 0bb6905a88784306878d9fceb0aa1c1ec68d1397 (tag: v21.11.3-rc1)
>        Author: Kevin Traynor <ktraynor@redhat.com>
>        Date:   Mon Dec 5 11:53:33 2022 +0000
>            version: 21.11.3-rc1
>            Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> 
> 
> NICs: X540-AT2 NIC(ixgbe, 10G)
> 
> 
> Best Regards,
> YangHang Liu
> 
> 
> On Tue, Dec 6, 2022 at 7:29 PM Kevin Traynor <ktraynor@redhat.com> wrote:
> 
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.3.
>>
>> The planned date for the final release is 19th December.
>>
>> 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.3-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>>      https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>



      reply	other threads:[~2022-12-19 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 11:29 Kevin Traynor
2022-12-13 11:48 ` Christian Ehrhardt
2022-12-15 10:19   ` Kevin Traynor
2022-12-15  3:44 ` Jiang, YuX
2022-12-15 10:35   ` Kevin Traynor
2022-12-15 17:51 ` Ali Alnubani
2022-12-19 10:40   ` Kevin Traynor
2022-12-16  7:55 ` YangHang Liu
2022-12-19 10:39   ` Kevin Traynor [this message]

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=b9472182-d6f3-46aa-9df0-5b5360a5ffd1@redhat.com \
    --to=ktraynor@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).