patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: YangHang Liu <yanghliu@redhat.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: 21.11.2 patches review and test
Date: Tue, 02 Aug 2022 10:32:24 +0100	[thread overview]
Message-ID: <35505c627a70714cb4a22b9d86ad2b1c2e529e18.camel@debian.org> (raw)
In-Reply-To: <CAGYh1E_5x6CGLkD5YtcLEgWq6t3m=Z0pyzrc=AHyBMNDkvAPCA@mail.gmail.com>

On Tue, 2022-08-02 at 11:29 +0800, YangHang Liu wrote:
> Hi Luca,
> 
> The dpdk 21.11.2-rc1 test result from Red Hat looks good.
> 
> 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 6.2
>  * dpdk: git://dpdk.org/dpdk-stable (remotes/origin/21.11)
>     - # git log
>       Author: Luca Boccassi <bluca@debian.org>
>       Date:   Mon Jul 18 09:56:26 2022 +0100
>       version: 21.11.2-rc1
>       Signed-off-by: Luca Boccassi <bluca@debian.org>
>  * NICs: X540-AT2 NIC(ixgbe, 10G)
> 
> 
> 
> Best Regards,
> YangHang Liu

Thank you!

> On Thu, Jul 28, 2022 at 8:34 PM Luca Boccassi <bluca@debian.org>
> wrote:
> > On Mon, 2022-07-18 at 10:58 +0100, luca.boccassi@gmail.com wrote:
> > > Hi all,
> > > 
> > > Here is a list of patches targeted for stable release 21.11.2.
> > > 
> > > The planned date for the final release is August 29th.
> > > 
> > > 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.2-rc1
> > > 
> > > These patches are located at branch 21.11 of dpdk-stable repo:
> > >     https://dpdk.org/browse/dpdk-stable/
> > > 
> > > Thanks.
> > > 
> > > Luca Boccassi
> > 
> > Hello,
> > 
> > Any update from any of the validation teams? Any indication on how
> > the
> > tests are going?
> > 


  reply	other threads:[~2022-08-02  9:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:58 luca.boccassi
2022-07-19  2:40 ` Pei Zhang
2022-07-28 12:34 ` Luca Boccassi
2022-07-28 12:48   ` Ali Alnubani
2022-08-16  7:33     ` Ali Alnubani
2022-08-16 10:05       ` Luca Boccassi
2022-07-29  3:00   ` Jiang, YuX
2022-07-29 11:26     ` Jiang, YuX
2022-08-02 10:00       ` Luca Boccassi
2022-08-02 10:14         ` Jiang, YuX
2022-08-04  7:28           ` Jiang, YuX
2022-08-16 11:39             ` Luca Boccassi
2022-08-17 10:00               ` Jiang, YuX
2022-08-26  8:13                 ` Jiang, YuX
2022-08-26  9:06                   ` Kevin Traynor
2022-08-02  3:29   ` YangHang Liu
2022-08-02  9:32     ` Luca Boccassi [this message]
2022-08-29 13:00 ` Stokes, Ian
2022-08-29 16:20   ` 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=35505c627a70714cb4a22b9d86ad2b1c2e529e18.camel@debian.org \
    --to=bluca@debian.org \
    --cc=dev@dpdk.org \
    --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).