patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	 NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] 20.11.1 patches review and test
Date: Mon, 08 Mar 2021 10:12:55 +0000	[thread overview]
Message-ID: <ffda695d178246099a184fcdbec7f871efa7f619.camel@debian.org> (raw)
In-Reply-To: <MWHPR12MB147246BAA2DB8A8A4EC00985DA949@MWHPR12MB1472.namprd12.prod.outlook.com>

On Sun, 2021-03-07 at 14:48 +0000, Ali Alnubani wrote:
> Hi,
> 
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, February 22, 2021 5:09 PM
> > To: stable@dpdk.org
> > Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> > Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@nvidia.com>;
> > benjamin.walker@intel.com; David Christensen <drc@linux.vnet.ibm.com>;
> > hariprasad.govindharajan@intel.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>; pingx.yu@intel.com; qian.q.xu@intel.com; Raslan
> > Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon
> > <thomas@monjalon.net>; yuan.peng@intel.com; zhaoyan.chen@intel.com
> > Subject: 20.11.1 patches review and test
> > 
> > Hi all,
> > 
> > Here is a list of patches targeted for stable release 20.11.1.
> > 
> > The planned date for the final release is the 8th of March.
> > 
> > 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.
> > 
> 
> The following is a list of tests that we ran on this release:
> 
> - Basic functionality:
>   Send and receive multiple types of traffic.
> - testpmd xstats counter test.
> - testpmd timestamp test.
> - Changing/checking link status through testpmd.
> - RTE flow tests:
>   Items:
>   - eth
>   - gre
>   - gre_key
>     gtp
>   - icmp
>   - icmp6
>   - ipv4
>   - ipv6
>   - ipv6_ext
>   - ipv6_frag_ext
>   - meta
>   - mpls
>   - nvgre
>   - tcp
>   - udp
>   - vlan
>   - vxlan
>   - vxlan-gpe
>   Actions:
>   - age (shared and non-shared)
>   - count
>   - dec_tcp_ack
>   - dec_tcp_seq
>   - dec_ttl
>   - drop
>   - flag
>   - inc_tcp_ack
>   - inc_tcp_seq
>   - jump
>   - mark
>   - meter
>   - of_pop_vlan
>   - of_push_vlan
>   - of_set_vlan_pcp
>   - of_set_vlan_vid
>   - queue
>   - raw_decap
>   - raw_encap
>   - rss (shared and non-shared)
>   - set_ipv4_dscp
>   - set_ipv4_dst
>   - set_ipv4_src
>   - set_ipv6_dscp
>   - set_ipv6_dst
>   - set_ipv6_src
>   - set_mac_dst
>   - set_mac_src
>   - set_meta
>   - set_tag
>   - set_tp_dst
>   - set_tp_src
>   - set_ttl
>   - vxlan_decap
>   - vxlan_encap
> - Some RSS tests.
> - VLAN filtering, stripping and insertion tests.
> - Checksum and TSO tests.
> - ptype tests.
> - link_status_interrupt example application tests.
> - l3fwd-power example application tests.
> - Multi-process example applications tests.
> 
> Functional tests ran on:
> - NIC: ConnectX-4 Lx / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.2-2.2.0.0 / Firmware: 14.29.2002
> - NIC: ConnectX-4 Lx / OS: RHEL7.4 / Kernel: 5.12.0-rc1 / Driver: rdma-core 34.0 / Firmware: 14.29.2002
> - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.2-2.2.0.0 / Firmware: 16.29.2002
> - NIC: ConnectX-5 / OS: RHEL7.4 / Kernel: 5.12.0-rc1 / Driver: rdma-core 34.0 / Firmware: 16.29.2002
> 
> Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
> - Ubuntu 20.04.1 with MLNX_OFED_LINUX-5.2-2.2.0.0.
> - Ubuntu 20.04.1 with rdma-core master (7f2d460).
> - Ubuntu 20.04.1 with rdma-core v28.0.
> - Ubuntu 18.04.5 with rdma-core v17.1.
> - Ubuntu 18.04.5 with rdma-core master (7f2d460) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 32 with rdma-core v33.0.
> - CentOS 7 7.9.2009 with rdma-core master (7f2d460).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.2-2.2.0.0.
> - CentOS 8 8.3.2011 with rdma-core master (7f2d460).
> - openSUSE Leap 15.2 with rdma-core v27.1.
> 
> We don't see any new issues in this release.
> 
> Regards,
> Ali

Thank you!

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2021-03-08 10:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 15:09 luca.boccassi
2021-02-25  9:43 ` [dpdk-stable] [dpdk-dev] " Christian Ehrhardt
2021-02-25 10:14   ` Luca Boccassi
2021-02-25 13:00 ` [dpdk-stable] " Pei Zhang
2021-02-25 14:39   ` Luca Boccassi
2021-03-02  6:23 ` [dpdk-stable] [dpdk-dev] " Kalesh Anakkur Purayil
2021-03-02 10:29   ` Luca Boccassi
2021-03-02 10:52 ` Chen, BoX C
2021-03-02 11:27   ` Luca Boccassi
2021-03-03  1:57     ` Chen, BoX C
2021-03-07 14:48 ` [dpdk-stable] " Ali Alnubani
2021-03-08 10:12   ` Luca Boccassi [this message]
2021-03-09 10:36 ` Govindharajan, Hariprasad

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=ffda695d178246099a184fcdbec7f871efa7f619.camel@debian.org \
    --to=bluca@debian.org \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).