From: Kevin Traynor <ktraynor@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"hariprasad.govindharajan@intel.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>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 21.11.1 patches review and test
Date: Wed, 13 Apr 2022 14:18:22 +0100 [thread overview]
Message-ID: <09ba28bc-d452-0e7d-6f79-b6874d91c485@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167FE520D98379F3C3C2826DAEA9@DM4PR12MB5167.namprd12.prod.outlook.com>
On 11/04/2022 12:00, Ali Alnubani wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Friday, April 1, 2022 1:22 PM
>> To: stable@dpdk.org
>> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.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>; qian.q.xu@intel.com; Raslan Darawsheh
>> <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
>> <thomas@monjalon.net>; yuan.peng@intel.com; zhaoyan.chen@intel.com
>> Subject: 21.11.1 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.1.
>>
>> Please try and complete validation by April 13th.
>>
>> 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.
>>
>
> Hello,
>
> We ran the following functional tests with Nvidia hardware on 21.11.1-rc1:
> - 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:
> - conntrack
> - ecpri
> - eth
> - flex
> - geneve
> - geneve_opt
> - gre
> - gre_key
> - gre_option
> - gtp
> - gtp_psc
> - icmp
> - icmp6
> - integrity
> - ipv4
> - ipv6
> - ipv6_frag_ext
> - mark
> - meta
> - mpls
> - nvgre
> - phy_port
> - port_id
> - tag
> - tcp
> - udp
> - vlan
> - vxlan
> - vxlan_gpe
>
> Actions:
> - age
> - conntrack
> - count
> - dec_tcp_ack
> - dec_tcp_seq
> - dec_ttl
> - drop
> - flag
> - inc_tcp_ack
> - inc_tcp_seq
> - jump
> - mark
> - meter
> - modify_field
> - nvgre_decap
> - nvgre_encap
> - of_pop_vlan
> - of_push_vlan
> - of_set_vlan_pcp
> - of_set_vlan_vid
> - port_id
> - queue
> - raw_decap
> - raw_encap
> - represented_port
> - rss
> - sample
> - 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.
> - Hardware LRO tests.
> - Regex application tests.
> - Buffer Split tests.
> - Tx scheduling tests.
>
> Functional tests ran on:
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 14.32.1010
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 16.32.2004
> - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 22.32.2004
> - DPU: BlueField-2 / DOCA SW version: 1.2.1
>
> Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations:
> - Ubuntu 20.04.4 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - Ubuntu 20.04.4 with rdma-core v39.0.
> - Ubuntu 20.04.4 with rdma-core v28.0.
> - Ubuntu 18.04.6 with rdma-core v17.1.
> - Ubuntu 18.04.6 with rdma-core master (5daf6a7) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 35 with rdma-core v39.0.
> - CentOS 7 7.9.2009 with rdma-core master (5daf6a7).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - CentOS 8 8.4.2105 with rdma-core master (5daf6a7).
> - OpenSUSE Leap 15.3 with rdma-core v31.0.
> - Windows Server 2019 with Clang 11.0.0.
>
> We don't see any new critical issues blocking this release.
>
Thanks for the report Ali.
Kevin.
> Thanks,
> Ali
>
next prev parent reply other threads:[~2022-04-13 13:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:22 Kevin Traynor
2022-04-11 3:03 ` Pei Zhang
2022-04-13 4:06 ` YangHang Liu
2022-04-13 13:20 ` Kevin Traynor
2022-04-11 6:58 ` Christian Ehrhardt
2022-04-13 7:26 ` Christian Ehrhardt
2022-04-13 8:44 ` Kevin Traynor
2022-04-13 10:06 ` Kevin Traynor
2022-04-14 5:52 ` Christian Ehrhardt
2022-04-14 7:17 ` Thomas Monjalon
2022-04-14 9:08 ` Kevin Traynor
2022-04-11 11:00 ` Ali Alnubani
2022-04-13 13:18 ` Kevin Traynor [this message]
2022-04-12 8:58 ` Jiang, YuX
2022-04-13 13:19 ` Kevin Traynor
2022-04-14 4:58 ` Jiang, YuX
2022-04-25 15:01 ` Kevin Traynor
2022-04-20 5:50 ` Christian Ehrhardt
2022-04-25 13:39 ` 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=09ba28bc-d452-0e7d-6f79-b6874d91c485@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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).