DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3
Date: Wed, 19 May 2021 10:45:07 +0000	[thread overview]
Message-ID: <DM4PR12MB51677778FC4AC8962F981D57DA2B9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <7142607.3L8AUzOtay@thomas>

Hi,

> -----Original Message-----
> From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> Monjalon
> Sent: Wednesday, May 12, 2021 11:57 PM
> To: announce@dpdk.org
> Subject: [dpdk-announce] release candidate 21.05-rc3
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v21.05-rc3
> 
> There are 114 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_21_05.html
> 
> Please test and report issues on bugs.dpdk.org.
> You may share some release validation results by replying to this message at
> dev@dpdk.org.
> 

The following is a list of tests that we ran on 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 tests:
  Items:
  - eth
  - geneve
  - gre
  - gre_key
  - gtp
  - gtp_psc
  - icmp
  - icmp6
  - ipv4
  - ipv6
  - ipv6_ext
  - ipv6_frag_ext
  - meta
  - mpls
  - nvgre
  - tcp
  - udp
  - vlan
  - vxlan
  - vxlan-gpe
  Actions:
  - age (shared and non-shared)
  - count
  - dec_tcp_ack
  - dec_tcp_seq
  - dec_ttl
  - drop
  - flag
  - inc_tcp_ack
  - inc_tcp_seq
  - jump
  - mark
  - meter
  - modify_field
  - of_pop_vlan
  - of_push_vlan
  - of_set_vlan_pcp
  - of_set_vlan_vid
  - port_id
  - queue
  - raw_decap
  - raw_encap
  - rss (shared and non-shared)
  - sample
  - set_ipv4_dscp
  - set_ipv4_dst
  - set_ipv4_src
  - set_ipv6_dscp
  - set_ipv6_dst
  - set_ipv6_src
  - set_mac_dst
  - set_mac_src
  - set_meta
  - set_tag
  - set_tp_dst
  - set_tp_src
  - set_ttl
  - vxlan_decap
  - vxlan_encap
- Some RSS tests.
- VLAN filtering, stripping and insertion tests.
- Checksum and TSO tests.
- ptype tests.
- link_status_interrupt example application tests.
- l3fwd-power example application tests.
- Multi-process example applications tests.
- Hardware LRO tests.
- Regex application tests.
- Buffer Split tests.
- Tx scheduling tests.

We don't see any critical issues blocking the release.

Thanks,
Ali

  parent reply	other threads:[~2021-05-19 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:57 Thomas Monjalon
2021-05-14 10:07 ` Jiang, YuX
2021-05-18  7:29   ` Jiang, YuX
2021-05-19  4:07 ` Thinh Tran
2021-05-19 10:45 ` Ali Alnubani [this message]
2021-05-20  7:34 ` Kalesh Anakkur Purayil

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=DM4PR12MB51677778FC4AC8962F981D57DA2B9@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.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).