From: Ali Alnubani <alialnu@nvidia.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.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>,
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" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Yanghang Liu <yanghliu@redhat.com>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: RE: 20.11.7 patches review and test
Date: Sun, 11 Dec 2022 16:15:36 +0000 [thread overview]
Message-ID: <DM4PR12MB5167788F52C16244C4161F16DA1E9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221128105232.1394896-1-luca.boccassi@gmail.com>
> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Monday, November 28, 2022 12:53 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>; 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>; Yanghang Liu <yanghliu@redhat.com>;
> yuan.peng@intel.com; zhaoyan.chen@intel.com
> Subject: 20.11.7 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 20.11.7.
>
> The planned date for the final release is the 12th of 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=v20.11.7-rc1
>
> These patches are located at branch 20.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Luca Boccassi
>
> ---
Hello,
We ran the following functional tests with Nvidia hardware on v20.11.7-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:
- eth
- geneve
- gre
- gre_key
- gtp
- icmp
- icmp6
- ipv4
- ipv6
- ipv6_frag_ext
- mark
- meta
- mpls
- nvgre
- tag
- tcp
- udp
- vlan
- vxlan
- vxlan_gpe
Actions:
- age
- count
- dec_tcp_ack
- dec_tcp_seq
- dec_ttl
- drop
- flag
- inc_tcp_ack
- inc_tcp_seq
- jump
- mark
- queue
- raw_decap
- raw_encap
- rss
- 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.
Functional tests ran on:
- NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.8-1.0.1.1 / Firmware: 14.32.1010
- NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.8-1.0.1.1 / Firmware: 16.35.1012
- NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.8-1.0.1.1 / Firmware: 22.35.1012
- DPU: BlueField-2 / DOCA SW version: 1.5.0 / Firmware: 24.35.1012
Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations:
- Ubuntu 22.04.1 with MLNX_OFED_LINUX-5.8-1.1.2.1.
- Ubuntu 20.04.5 with MLNX_OFED_LINUX-5.8-1.1.2.1.
- Ubuntu 20.04.5 with rdma-core master (76cfaa1).
- Ubuntu 20.04.5 with rdma-core v28.0.
- Ubuntu 18.04.6 with rdma-core v17.1.
- Ubuntu 18.04.6 with rdma-core master (76cfaa1) (i386).
- Ubuntu 16.04.7 with rdma-core v22.7.
- Fedora 37 with rdma-core v41.0.
- Fedora 38 (Rawhide) with rdma-core v41.0.
- CentOS 7 7.9.2009 with rdma-core master (76cfaa1).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.8-1.0.1.1.
- CentOS 8 8.4.2105 with rdma-core master (76cfaa1).
- OpenSUSE Leap 15.4 with rdma-core v38.1.
- Windows Server 2019 with Clang 11.0.0.
The builds are passing except for debug builds on Fedora with gcc 12:
lib/librte_ring/rte_ring_elem.h:194:25: error: 'memcpy' reading 32 bytes from a region of size 4 [-Werror=stringop-overread]
Please note that not all the functional tests mentioned above fall under "Basic functionality with testpmd" like reported in the release notes for previous releases:
https://git.dpdk.org/dpdk-stable/commit/?h=v20.11.6&id=73655c6414914c99a33010e9e7bdae9cafd24404
Some of them test other example apps.
We don't see new issues caused by the changes in this release.
Thanks,
Ali
next prev parent reply other threads:[~2022-12-11 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 10:52 luca.boccassi
2022-11-28 11:35 ` Morten Brørup
2022-11-28 11:55 ` Luca Boccassi
2022-11-28 12:07 ` Morten Brørup
2023-04-11 7:22 ` Morten Brørup
2023-04-11 9:58 ` Luca Boccassi
2022-12-11 16:15 ` Ali Alnubani [this message]
2022-12-12 20:00 ` Luca Boccassi
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=DM4PR12MB5167788F52C16244C4161F16DA1E9@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.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=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yanghliu@redhat.com \
--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).