patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ali Alnubani <alialnu@mellanox.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>,
	Thomas Monjalon <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-stable] 18.11.9 (LTS) patches review and test
Date: Tue, 30 Jun 2020 10:52:32 +0100	[thread overview]
Message-ID: <594515b4-5321-8fc6-c12c-645a65091a19@redhat.com> (raw)
In-Reply-To: <AM0PR05MB440134068E5C5BB4E2117BC7D76F0@AM0PR05MB4401.eurprd05.prod.outlook.com>

On 30/06/2020 09:54, Ali Alnubani wrote:
> Hi,
> 

Hi Ali,

Thanks for testing.

>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Friday, June 26, 2020 3:53 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>; Thomas
>> Monjalon <thomas@monjalon.net>; yuan.peng@intel.com;
>> zhaoyan.chen@intel.com
>> Subject: 18.11.9 (LTS) patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for LTS release 18.11.9.
>>
>> The planned date for the final release is 3rd July.
>>
>> 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.
>>
> 
> We ran the following tests on Mellanox hardware for this version:
> - 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:
>   Items: eth / vlan / ipv4 / ipv6 / tcp / udp / gre
>   Actions: drop / queue / rss / mark / flag
> - Some RSS tests.
> - VLAN stripping and insertion tests.
> - Checksum and TSO tests.
> - ptype tests.
> - l3fwd-power example application tests.
> - Multi-process example applications tests.
> 
> Testing matrix:
> - NIC: ConnectX-4 Lx / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.0-2.1.8.0 / Firmware: 14.27.1016
> - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.0-2.1.8.0 / Firmware: 16.27.2008
> 
> We found 2 issues:
> - Failure to restart ports with kernels newer than 5.6 (call to mmap failed on UAR for txq).
> - Applications fail to start with CONFIG_RTE_LIBRTE_MLX5_DEBUG enabled (mlx5_ifindex: Assertion `priv->if_index' failed).

Are these regressions? i.e. does 18.11.8 fail in the same way in the
same testbed

> We are discussing these issues internally, and we see no other regressions blocking the release.
> 

ok, please let me know the outcome and if any patches need to be
added/removed to resolve these issues.

thanks,
Kevin.

> Regards,
> Ali
> 


  reply	other threads:[~2020-06-30  9:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 12:53 Kevin Traynor
2020-06-28  3:51 ` Chen, BoX C
2020-06-29  9:03   ` Kevin Traynor
2020-06-28  5:42 ` Pei Zhang
2020-06-29  9:04   ` Kevin Traynor
2020-06-30  8:54 ` Ali Alnubani
2020-06-30  9:52   ` Kevin Traynor [this message]
2020-06-30 10:02     ` Ali Alnubani
2020-07-10  8:53       ` Kevin Traynor
2020-06-30 15:38 ` [dpdk-stable] [dpdk-dev] " Govindharajan, Hariprasad
2020-06-30 16:21   ` Kevin Traynor
2020-06-30 16:32     ` Stokes, Ian
2020-06-30 17:03       ` Kevin Traynor
2020-07-06 15:57         ` Kevin Traynor
2020-07-03 17:26 ` [dpdk-stable] " Kevin Traynor
2020-07-10 17:28 ` [dpdk-stable] [EXTERNAL] " Abhishek Marathe
2020-07-10 17:51   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2020-06-20 12:52 [dpdk-stable] " 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=594515b4-5321-8fc6-c12c-645a65091a19@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alialnu@mellanox.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=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=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).