DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"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>,
	"yanghliu@redhat.com" <yanghliu@redhat.com>,
	 "yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 19.11.14 patches review and test
Date: Tue, 13 Dec 2022 12:28:37 +0100	[thread overview]
Message-ID: <CAATJJ0J_J9At43KVQuSF0XH96-r-oQwBBFCV-a4Nki9vcrvA5w@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB5167FDBEAE73AA6670C2543FDA1E9@DM4PR12MB5167.namprd12.prod.outlook.com>

Thank you all so much - @ Jiang YuX, YangHang Liu, Ali Alnubani !

To add my own that just completed last night:

Same tests as usual, no regressions found:

19.11.14~rc1-0ubuntu0.20.04.1~focalppa1

1.0.0 (14:11:38): phys (BM) tests
  1.1.0 (14:11:38): initialize environment
    1.1.1 (14:14:57): testpmd  => Pass
    1.1.2 (14:16:32): check testpmd output  => Pass
2.0.0 (14:16:32): prep virtual test environment

1.0.0 (14:18:56): virt tests
  1.1.0 (14:18:56): initialize environment
3.0.0 (14:19:51): performance tests
  3.1.0 (14:19:51): prep benchmarks
  3.2.0 (14:21:53): performance tests
    3.2.1 (14:22:01): test guest-openvswitch for OVS-5CPU  => Pass
    3.2.2 (14:41:19): test guest-dpdk-vhost-user-client-multiq for
OVSDPDK-VUC  => Pass
4.0.0 (15:02:00): VUC endurance checks
  4.1.0 (15:02:00): prep VUC endurance tests
    4.1.1 (15:15:27): start stop guests (client)  => Pass
    4.1.2 (16:37:07): add/remove ports (client)  => Pass
  4.2.0 (16:46:39): Final cleanup


On Sun, Dec 11, 2022 at 3:40 PM Ali Alnubani <alialnu@nvidia.com> wrote:
>
> > -----Original Message-----
> > From: christian.ehrhardt@canonical.com
> > <christian.ehrhardt@canonical.com>
> > Sent: Monday, November 28, 2022 3:17 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>; yanghliu@redhat.com; yuan.peng@intel.com;
> > zhaoyan.chen@intel.com
> > Subject: 19.11.14 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 19.11.14.
> >
> > The planned date for the final release is Tue 12th December 2022.
> >
> > 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=v19.11.14-rc1
> >
> > These patches are located at branch 19.11 of dpdk-stable repo:
> >     https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Christian Ehrhardt <christian.ehrhardt@canonical.com>
> >
> > ---
>
> Hello,
>
> We ran the following functional tests with Nvidia hardware on 19.11.14-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 / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / geneve / vxlan / mplsoudp / mplsogre
>   Actions: drop / queue / rss / mark / flag / jump / count / raw_encap / raw_decap / vxlan_encap / vxlan_decap / NAT / dec_ttl
> - 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: 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
>
> Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations, and they are passing:
> - 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.
> - 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.
>
> We don't see any issues introduced by changes in this release.
>
> Builds on Fedora with gcc 12 and clang 15 are failing.
>
> 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=v19.11.13&id=104f5e8eb81e975809476fe894fc2781538ab752
>
> The following patch was missed in 19.11.13:
> https://inbox.dpdk.org/stable/DM4PR12MB516765207EE7A8999B284B5EDA1A9@DM4PR12MB5167.namprd12.prod.outlook.com/
>
> Thanks,
> Ali



-- 
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2022-12-13 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 13:16 christian.ehrhardt
2022-12-07 10:26 ` Jiang, YuX
2022-12-13 11:34   ` Christian Ehrhardt
2022-12-09  9:46 ` YangHang Liu
2022-12-11 14:40 ` Ali Alnubani
2022-12-13 11:28   ` Christian Ehrhardt [this message]
2022-12-13 11:41   ` Christian Ehrhardt
2022-12-13 19:46     ` Ali Alnubani

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=CAATJJ0J_J9At43KVQuSF0XH96-r-oQwBBFCV-a4Nki9vcrvA5w@mail.gmail.com \
    --to=christian.ehrhardt@canonical.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=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=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).