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: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Ali Alnubani <alialnu@nvidia.com>
Subject: RE: release candidate 22.11-rc3
Date: Sun, 20 Nov 2022 15:47:10 +0000	[thread overview]
Message-ID: <MWHPR12MB1181C79B704492A47E914A23D60B9@MWHPR12MB1181.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1720725.X513TT2pbd@thomas>

Hi,

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, November 15, 2022 7:33 PM
> To: announce@dpdk.org
> Subject: release candidate 22.11-rc3
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v22.11-rc3
> 
> There are 161 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_22_11.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 and by adding tested hardware in the release notes.
> 
> DPDK 22.11-rc4 should be the last chance for bug fixes and doc updates, and
> it is planned for the end of this week.
> 
> 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. - passed
- testpmd xstats counter test. - passed
- testpmd timestamp test. - passed
- Changing/checking link status through testpmd. - passed

- RTE flow tests:

  Matching on:
  - ecpri:  - sync is passed
  - eth: sync and async are passed
  - flex: sync is passed
  - geneve: sync is passed
  - geneve_opt: sync is passed
  - gre : sync and async are passed
  - gre_key: sync and async are passed
  - gre_option: sync is passed
  - gtp: sync and async are passed
  - gtp_psc: sync and async are passed
  - icmp: sync is passed
  - icmp6: sync is passed
  - integrity: sync and async are passed
  - ipv4: sync and async are passed
  - ipv6: sync and async are passed
  - ipv6_frag_ext: sync is passed
  - mark: sync and async are passed
  - meta: sync and async are passed
  - mpls: sync is passed
  - nvgre: sync and async are passed
  - phy_port: sync is passed
  - port_id: sync is passed
  - represented port: async is passed
  - tag: sync and async are passed
  - tcp: sync and async are passed
  - udp: sync and async are passed
  - vlan: sync and async are passed
  - vxlan: sync and async are passed
  - vxlan_gpe: sync and async are passed
  - esp: sync and async are passed

  Actions:
  - age: sync is passed
  - count: sync and async are passed
  - dec_tcp_ack: sync is passed
  - dec_tcp_seq: sync is passed
  - dec_ttl: sync is passed
  - drop: sync and async is passed
  - flag: sync is passed
  - inc_tcp_ack: sync is passed
  - inc_tcp_seq: sync is passed
  - jump: sync and async are passed
  - mark: sync and async are passed
  - meter: sync is passed
  - modify_field: sync and async are passed
  - nvgre_decap: sync is passed
  - nvgre_encap: sync is passed
  - of_pop_vlan: sync and async are passed
  - of_push_vlan: sync and async are passed
  - of_set_vlan_pcp: sync and async are passed
  - of_set_vlan_vid: sync and async are passed
  - port_id: sync and async are passed
  - queue: sync and async are passed
  - raw_decap: sync and async are passed
  - raw_encap: sync and async are passed
  - represented_port: async are passed
  - rss: sync and async are passed
  - sample: sync is passed
  - set_ipv4_dscp: sync is passed
  - set_ipv4_dst: sync is passed
  - set_ipv4_src: sync is passed
  - set_ipv6_dscp: sync is passed
  - set_ipv6_dst: sync is passed
  - set_ipv6_src: sync is passed
  - set_mac_dst: sync is passed
  - set_mac_src: sync is passed
  - set_meta: sync is passed
  - set_tag: sync is passed
  - set_tp_dst: sync is passed
  - set_tp_src: sync is passed
  - set_ttl: sync is passed
  - vxlan_decap: sync and async are passed
  - vxlan_encap: sync and async are passed

- RSS testing. -passed
- VLAN filtering, stripping and insertion tests. -passed
- Checksum and TSO tests. -passed
- ptype reporting -passed
- link status interrupt using the example application link_status_interrupt tests. - passed
- Interrupt mode using l3fwd-power example application tests. - passed
- Multi process testing using multi process example applications. - passed
- Hardware LRO tests. - passed
- Regex tests. - passed
- Buffer Split. - passed
- Tx scheduling. - passed

Kindest Regards,
Wael Abualrub

  parent reply	other threads:[~2022-11-20 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 17:32 Thomas Monjalon
2022-11-17  8:20 ` David Marchand
2022-11-17  8:48 ` Jiang, YuX
2022-11-21 13:50   ` Jiang, YuX
2022-11-21 14:13     ` Ferruh Yigit
2022-11-22 10:17     ` Jiang, YuX
2022-11-20 15:47 ` Wael Abualrub [this message]
2022-11-21 20:22 ` Thinh Tran

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=MWHPR12MB1181C79B704492A47E914A23D60B9@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).