DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.11-rc4
Date: Thu, 28 Nov 2019 12:25:04 +0000	[thread overview]
Message-ID: <AM0PR05MB44013E53821931BC0F7FA4F9D7470@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <2848553.yd9UBBcNlK@xps>

Hi,

> -----Original Message-----
> From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> Monjalon
> Sent: Wednesday, November 27, 2019 1:56 AM
> To: announce@dpdk.org
> Subject: [dpdk-announce] release candidate 19.11-rc4
> 
> A new DPDK release candidate is ready for testing:

The following covers the tests that we ran on Mellanox hardware for this version:

- 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
  Actions: drop / queue / rss / mark / flag / jump / count / port_id / raw_encap / raw_decap / vxlan_encap / vxlan_decap / NAT
- Some RSS tests.
- VLAN stripping and insertion tests.
- Checksum and TSO tests.
- ptype tests.
- Port interrupt testing.
- Multi-process testing.

Regards,
Ali

      parent reply	other threads:[~2019-11-28 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 23:56 Thomas Monjalon
2019-11-27 18:16 ` Stokes, Ian
2019-11-28  9:51 ` Luca Boccassi
2019-11-28 10:29   ` Sachin Saxena
2019-11-28 13:14   ` Xu, Qian Q
2019-11-28 12:25 ` 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=AM0PR05MB44013E53821931BC0F7FA4F9D7470@AM0PR05MB4401.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=dev@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).