DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Akhil Goyal <akhil.goyal@nxp.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>,
	"Luca Boccassi" <bluca@debian.org>,
	Pei Zhang <pezhang@redhat.com>,
	"pingx.yu@intel.com" <pingx.yu@intel.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
	"hariprasad.govindharajan@intel.com"
	<hariprasad.govindharajan@intel.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-dev] [dpdk-stable] 18.11.11 (LTS) patches review and test
Date: Wed, 20 Jan 2021 10:55:00 +0000
Message-ID: <MWHPR12MB1472CEE678ECA88AEB8AEEAEDAA20@MWHPR12MB1472.namprd12.prod.outlook.com> (raw)
In-Reply-To: <997da7c9-072c-23fa-e142-88e96ec3f8e2@redhat.com>

Hi Kevin,

> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Thursday, January 14, 2021 6:55 PM
> To: Ali Alnubani <alialnu@nvidia.com>; stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.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>; Luca Boccassi <bluca@debian.org>;
> Pei Zhang <pezhang@redhat.com>; pingx.yu@intel.com;
> qian.q.xu@intel.com; Raslan Darawsheh <rasland@mellanox.com>; NBU-
> Contact-Thomas Monjalon <thomas@monjalon.net>; yuan.peng@intel.com;
> zhaoyan.chen@intel.com; hariprasad.govindharajan@intel.com; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Asaf Penso <asafp@nvidia.com>
> Subject: Re: [dpdk-stable] 18.11.11 (LTS) patches review and test
> 
> On 14/01/2021 15:11, Ali Alnubani wrote:
> > Hi,
> >
> 
> Hi Ali,
> 
> >> -----Original Message-----
> >> From: stable <stable-bounces@dpdk.org> On Behalf Of Kevin Traynor
> >> Sent: Thursday, December 17, 2020 2:03 PM
> >> To: stable@dpdk.org
> >> Cc: dev@dpdk.org; Abhishek Marathe
> <Abhishek.Marathe@microsoft.com>;
> >> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani
> >> <alialnu@mellanox.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>;
> >> pingx.yu@intel.com; qian.q.xu@intel.com; Raslan Darawsheh
> >> <rasland@mellanox.com>; NBU- Contact-Thomas Monjalon
> >> <thomas@monjalon.net>; yuan.peng@intel.com;
> zhaoyan.chen@intel.com;
> >> hariprasad.govindharajan@intel.com
> >> Subject: [dpdk-stable] 18.11.11 (LTS) patches review and test
> >>
> >> Hi all,
> >>
> >> Here is a list of patches targeted for LTS release 18.11.11.
> >>
> >> The planned date for the final release is 19th January.
> >>
> >> Note, this is the last planned release of 18.11 LTS, and it will be
> >> unmaintained after this release, so I encourage anyone who is using
> >> 18.11 LTS to test.
> >>
> >> 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 covers the functional tests that we ran on Mellanox
> hardware for this release:
> > - Basic functionality:
> >   Send and receive multiple types of traffic.
> > - testpmd xstats counter tests.
> > - testpmd timestamp tests.
> > - Changing/checking link status through testpmd.
> > - RTE flow and flow_director tests.
> > - Some RSS tests.
> > - VLAN stripping and insertion tests.
> > - Checksum and TSO tests.
> > - ptype 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-1.0.4.0 / Firmware: 14.29.1016
> > - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.2-1.0.4.0
> > / Firmware: 16.29.1016
> >
> 
> Thanks for your testing.
> 
> > We don't see any issues introduced by the new changes in this release,
> however, we found the following issues while testing due to environment
> changes:
> > - Bug 615 - testpmd gets stuck when deleting an FDIR flow -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D615&amp;data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681676672%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&amp;sdata=4DWeo1yuZd7Y1%2BgfkX4vkTQGkrqtYLPFR
> 4KBTb2J5Us%3D&amp;reserved=0 - Won't fix.
> > - Bug 616 - [mlx5] packet does not match a corresponding rte_flow rule due
> to inner ether_type spec validation -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D616&amp;data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&amp;sdata=EzIwmXI5Fd9o2AA33sU26MNrYOBbgTugfh
> Cm0gHFzEA%3D&amp;reserved=0 - Won't fix.
> > - Bug 617 - [mlx5] packet does not match a corresponding rte_flow rule due
> to vxlan vni spec validation -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D617&amp;data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&amp;sdata=dCdR2epT0kOoTXs%2B2hrOZeTBtMI8jVHP6
> uKYKtTzbkA%3D&amp;reserved=0 - Won't fix.
> 
> We can put these in the known issues section of the release notes.
> 
> > - Bug 618 - [mlx5] secondary process fails to start -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D618&amp;data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&amp;sdata=Akc9dviCGiCfqbuFJZLbsC8%2BU394q9jYOKr
> fbOZlBXk%3D&amp;reserved=0 - We are still looking into this.
> >
> 
> Ok, I'll keep an eye on the Bz and please add me on Cc: if there are patches
> to fix it and I can run them through the 18.11 build checks etc.
> 

Ran all my tests again on latest (660b995) and didn't see any new issues.

Thanks,
Ali

      reply	other threads:[~2021-01-20 10:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:03 [dpdk-dev] " Kevin Traynor
2020-12-23  9:41 ` Pei Zhang
2021-01-05 16:24   ` Kevin Traynor
2020-12-29  9:01 ` Chen, BoX C
2021-01-05 16:23   ` Kevin Traynor
2021-01-06  2:08     ` Chen, BoX C
2021-01-12  9:45 ` Kevin Traynor
2021-01-14 14:32 ` Govindharajan, Hariprasad
2021-01-14 16:50   ` Kevin Traynor
2021-01-14 15:11 ` [dpdk-dev] [dpdk-stable] " Ali Alnubani
2021-01-14 16:55   ` Kevin Traynor
2021-01-20 10:55     ` Ali Alnubani [this message]

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=MWHPR12MB1472CEE678ECA88AEB8AEEAEDAA20@MWHPR12MB1472.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=asafp@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=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=pingx.yu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git