DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wael Abualrub <waela@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: Raslan Darawsheh <rasland@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Subject: RE: release candidate 22.07-rc4
Date: Sun, 17 Jul 2022 14:33:20 +0000	[thread overview]
Message-ID: <MWHPR12MB11817171919200E76E7DD56ED68D9@MWHPR12MB1181.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6125682.jrt8l4j9yI@thomas>

Hi,

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, July 12, 2022 1:37 AM
> To: announce@dpdk.org
> Subject: release candidate 22.07-rc4
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v22.07-rc4
> 
> There are 22 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_22_07.html
> 
> This is the last release candidate.
> Only documentation should be updated before the release.
> 
> Reviews of deprecation notices are required:
> https://patches.dpdk.org/bundle/dmarchand/deprecation_notices/
> 
> You may share some release validation results by replying to this message at
> dev@dpdk.org and by adding tested hardware in the release notes.
> 
> Please think about sharing your roadmap now for DPDK 22.11.
> 
> Thank you everyone
> 

The following is a list of tests that we ran on NVIDIA hardware 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:
  - conntrack
  - ecpri
  - eth
  - flex
  - geneve
  - geneve_opt
  - gre
  - gre_key
  - gre_option
  - gtp
  - gtp_psc
  - icmp
  - icmp6
  - integrity
  - ipv4
  - ipv6
  - ipv6_frag_ext
  - mark
  - meta
  - mpls
  - nvgre
  - phy_port
  - port_id
  - tag
  - tcp
  - udp
  - vlan
  - vxlan
  - vxlan_gpe
  - esp

  Actions:
  - age
  - conntrack
  - count
  - dec_tcp_ack
  - dec_tcp_seq
  - dec_ttl
  - drop
  - flag
  - inc_tcp_ack
  - inc_tcp_seq
  - jump
  - mark
  - meter
  - modify_field
  - nvgre_decap
  - nvgre_encap
  - of_pop_vlan
  - of_push_vlan
  - of_set_vlan_pcp
  - of_set_vlan_vid
  - port_id
  - queue
  - raw_decap
  - raw_encap
  - represented_port
  - rss
  - 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.

PS: We are internally investigating a few test failures, and we'll send fixes if necessary.

Kindest Regards,
Wael Abualrub

      parent reply	other threads:[~2022-07-17 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 22:36 Thomas Monjalon
2022-07-12  9:32 ` Jiang, YuX
2022-07-12  9:44   ` Xia, Chenbo
2022-07-14  8:17     ` Jiang, YuX
2022-07-15  7:59       ` Jiang, YuX
2022-07-15 14:18 ` Thinh Tran
2022-07-17 14:33 ` Wael Abualrub [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=MWHPR12MB11817171919200E76E7DD56ED68D9@MWHPR12MB1181.namprd12.prod.outlook.com \
    --to=waela@nvidia.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=rasland@nvidia.com \
    --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).