DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: DPDK 23.03 released
Date: Fri, 31 Mar 2023 19:17:21 +0200	[thread overview]
Message-ID: <8105645.8F6SAcFxjW@thomas> (raw)

A new major release is available:
	https://fast.dpdk.org/rel/dpdk-23.03.tar.xz

Winter release numbers are quite small as usual:
	1048 commits from 161 authors
	1379 files changed, 85721 insertions(+), 25814 deletions(-)

It is not planned to start a maintenance branch for 23.03.
This version is ABI-compatible with 22.11.

Below are some new features:
	- lock annotations
	- ARM power management monitor/wakeup
	- machine learning inference device API and test application
	- platform bus
	- 400G link speed
	- queue mapping of aggregated ports
	- flow quota
	- more flow matching (ICMPv6, IPv6 routing extension)
	- more flow actions (flex modify, congestion management)
	- Intel cpfl IPU driver
	- Marvell CNXK machine learning inference
	- SHAKE hash algorithm for crypto
	- LZ4 algorithm for compression
	- more telemetry endpoints
	- more tracepoints
	- DTS hello world

More details in the release notes:
	https://doc.dpdk.org/guides/rel_notes/release_23_03.html

The test framework DTS is being improved and migrated into the mainline.
Please join the DTS effort for contributing, reviewing or testing.


There are 34 new contributors (including authors, reviewers and testers).
Welcome to Alok Prasad, Alvaro Karsz, Anup Prabhu, Boleslav Stankevich,
Boris Ouretskey, Chenyu Huang, Edwin Brossette, Fengnan Chang,
Francesco Mancino, Haijun Chu, Hiral Shah, Isaac Boukris, J.J. Martzki,
Jesna K E, Joshua Washington, Kamalakshitha Aligeri, Krzysztof Karas,
Leo Xu, Maayan Kashani, Michal Schmidt, Mohammad Iqbal Ahmad,
Nathan Brown, Patrick Robb, Prince Takkar, Rushil Gupta,
Saoirse O'Donovan, Shivah Shankar S, Shiyang He, Song Jiale,
Vikash Poddar, Visa Hankala, Yevgeny Kliteynik, Zerun Fu,
and Zhuobin Huang.

Below is the number of commits per employer (with authors count):
	265     Marvell (33)
	256     Intel (49)
	175     NVIDIA (20)
	 98     Red Hat (6)
	 68     Huawei (3)
	 55     Corigine (9)
	 49     Microsoft (3)
	 13     Arm (5)
	 10     PANTHEON.tech (1)
	  9     Trustnet (1)
	  9     AMD (2)
	  8     Ark Networks (2)
	        ...

A big thank to all courageous people who took on the non rewarding task
of reviewing other's job.
Based on Reviewed-by and Acked-by tags, the top non-PMD reviewers are:
	 48     Maxime Coquelin <maxime.coquelin@redhat.com>
	 46     Ferruh Yigit <ferruh.yigit@amd.com>
	 44     Morten Brørup <mb@smartsharesystems.com>
	 25     Ori Kam <orika@nvidia.com>
	 24     Tyler Retzlaff <roretzla@linux.microsoft.com>
	 23     Chengwen Feng <fengchengwen@huawei.com>
	 21     David Marchand <david.marchand@redhat.com>
	 21     Akhil Goyal <gakhil@marvell.com>


The next version will be 23.07 in July.
The new features for 23.07 can be submitted during the next 3 weeks:
        http://core.dpdk.org/roadmap#dates
Please share your roadmap.

One last ask; please fill this quick survey before April 7th
to help planning the next DPDK Summit:
https://docs.google.com/forms/d/1104swKV4-_nNT6GimkRBNVac1uAqX7o2P936bcGsgMc

Thanks everyone



                 reply	other threads:[~2023-03-31 17:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8105645.8F6SAcFxjW@thomas \
    --to=thomas@monjalon.net \
    --cc=announce@dpdk.org \
    /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).