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.6 (LTS) patches review and test
Date: Thu, 9 Jan 2020 13:41:53 +0000	[thread overview]
Message-ID: <38bb4b05-e076-1ad5-4d0d-7e8e39c14b55@redhat.com> (raw)
In-Reply-To: <AM0PR05MB4401F0B2A5D3552D0D992A54D72B0@AM0PR05MB4401.eurprd05.prod.outlook.com>

On 26/12/2019 13:35, Ali Alnubani wrote:
> Hi,
> 
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Wednesday, December 18, 2019 1:42 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.6 (LTS) patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for LTS release 18.11.6.
>>
>> The planned date for the final release is 31st January.
>>
>> 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 tests that we ran on Mellanox hardware for this version:

Thanks Ali. I am assuming they passed too ;-)

btw, the clang 9 issue you fixed on master was present on 18.11, so I
will add your patch (unless objections)

> - Verify sending and receiving 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.
> - Multi-process tests.
> 
> The tests ran on (OS: RHEL7.4 | Kernel: Linux 3.10.0-693.el7.x86_64 | Driver: MLNX_OFED_LINUX-4.7-3.2.9.0).
> 
> NICs tested:
> - ConnectX-5 | Firmware: 16.26.4012
> - ConnectX-4 Lx | Firmware: 14.26.4012
> 
> Regards,
> Ali
> 


  reply	other threads:[~2020-01-09 13:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 11:42 Kevin Traynor
2019-12-24 10:07 ` Yu, PingX
2020-01-08 18:32   ` Kevin Traynor
2020-01-08 18:34   ` Kevin Traynor
2020-01-09  8:30     ` Julien Meunier
2020-01-09 14:18       ` Kevin Traynor
2020-01-09 17:10         ` Trahe, Fiona
2019-12-25  5:17 ` Pei Zhang
     [not found]   ` <BN8PR21MB1217C1C2EF180C4D29DAF216DA280@BN8PR21MB1217.namprd21.prod.outlook.com>
     [not found]     ` <HK0P153MB0290B7D0487D922C3854BAF7E7270@HK0P153MB0290.APCP153.PROD.OUTLOOK.COM>
     [not found]       ` <MN2PR21MB123271BB60DB0E70ACD2FA91DA270@MN2PR21MB1232.namprd21.prod.outlook.com>
     [not found]         ` <HK0P153MB0290EECF6665FA00EC22867BE7270@HK0P153MB0290.APCP153.PROD.OUTLOOK.COM>
     [not found]           ` <MN2PR21MB123240BDE6BA187B4DE15F55DA270@MN2PR21MB1232.namprd21.prod.outlook.com>
2019-12-30  8:56             ` Lili Deng
2020-01-09 14:03               ` Kevin Traynor
2020-01-09 17:32                 ` [dpdk-stable] [EXTERNAL] " Ju-Hyoung Lee
2020-01-09 13:38   ` [dpdk-stable] " Kevin Traynor
2019-12-26 13:35 ` Ali Alnubani
2020-01-09 13:41   ` Kevin Traynor [this message]
2020-01-14 14:40 ` Kevin Traynor
2020-01-19  5:31   ` Yu, PingX
2020-01-19 21:05     ` Kevin Traynor
2020-01-30 14:58   ` Stokes, Ian

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=38bb4b05-e076-1ad5-4d0d-7e8e39c14b55@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).