DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@mellanox.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@mellanox.com>,
	 Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] 19.11.1 patches review and test
Date: Tue, 10 Mar 2020 14:06:44 +0000	[thread overview]
Message-ID: <85197149896a0819667230f04266854fcd4fe37c.camel@debian.org> (raw)
In-Reply-To: <AM0PR05MB440168CBCD4BC8F258783532D7FF0@AM0PR05MB4401.eurprd05.prod.outlook.com>

On Tue, 2020-03-10 at 13:26 +0000, Ali Alnubani wrote:
> Hi Luca,
> 
> > -----Original Message-----
> > From: 
> > luca.boccassi@gmail.com
> >  <
> > luca.boccassi@gmail.com
> > >
> > Sent: Monday, March 2, 2020 1:11 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: 19.11.1 patches review and test
> > 
> > Hi all,
> > 
> > Here is a list of patches targeted for stable release 19.11.1.
> > 
> > The planned date for the final release is March the 16th.
> > 
> > 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 release:
> 
> - Basic functionality:
>   Send and receive multiple types of traffic.
> - testpmd xstats counter test.
> - testpmd timestamp test.
> - Changing/checking link status through testpmd.
> - RTE flow and flow_director tests.
>   Items: eth / vlan / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre /
> vxlan / geneve / ip in ip / mplsoudp / mplsogre / gtp
>   Actions: drop / queue / rss / mark / flag / jump / count / port_id
> / raw_encap / raw_decap / vxlan_encap / vxlan_decap / NAT / dec_ttl /
> set_dscp
> - 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-
> 1.0.0.0 / Firmware: 14.27.1016
> - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.0-1.0.0.0 
> / Firmware: 16.27.1016
> 
> We don't see any critical issues blocking the release.
> 
> Thanks,
> Ali

Thank you!

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2020-03-10 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 11:10 luca.boccassi
2020-03-06  6:55 ` Pei Zhang
2020-03-06 10:10   ` Luca Boccassi
     [not found] ` <67D543A150B29E4CAAE53918F64EDAEA3782789C@SHSMSX103.ccr.corp.intel.com>
2020-03-10 10:13   ` Yu, PingX
2020-03-10 10:42     ` Luca Boccassi
2020-03-10 13:26 ` Ali Alnubani
2020-03-10 14:06   ` Luca Boccassi [this message]
2020-03-11  3:28 ` Kalesh Anakkur Purayil
2020-03-11 10:42   ` Luca Boccassi
2020-03-12 15:16 ` Thinh Tran
2020-03-12 16:32   ` 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=85197149896a0819667230f04266854fcd4fe37c.camel@debian.org \
    --to=bluca@debian.org \
    --cc=alialnu@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).