DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: DPDK 22.03 released
Date: Thu, 17 Mar 2022 10:54:41 +0100	[thread overview]
Message-ID: <2392757.yKVeVyVuyW@thomas> (raw)

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

Winter release numbers are quite small as usual:
	956 commits from 181 authors
	2289 files changed, 83849 insertions(+), 97801 deletions(-)

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

Below are some new features:
	- fast restart by reusing hugepages
	- UDP/TCP checksum on multi-segments
	- IP reassembly offload
	- queue-based priority flow control
	- flow API for templates and async operations
	- private ethdev driver info dump
	- private user data in asymmetric crypto session

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


There are 51 new contributors (including authors, reviewers and testers).
Welcome to Abhimanyu Saini, Adham Masarwah, Asaf Ravid, Bin Zheng,
Brian Dooley, Brick Yang, Bruce Merry, Christophe Fontaine,
Chuanshe Zhang, Dawid Gorecki, Daxue Gao, Geoffrey Le Gourriérec,
Gerry Gribbon, Harold Huang, Harshad Narayane, Igor Chauskin,
Jakub Poczatek, Jeff Daly, Jie Hai, Josh Soref, Kamalakannan R,
Karl Bonde Torp, Kevin Liu, Kumara Parameshwaran, Madhuker Mythri,
Markus Theil, Martijn Bakker, Maxime Gouin, Megha Ajmera, Michael Barker,
Michal Wilczynski, Nan Zhou, Nobuhiro Miki, Padraig Connolly, Peng Yu,
Peng Zhang, Qiao Liu, Rahul Bhansali, Stephen Douthit, Tianli Lai,
Tudor Brindus, Usama Arif, Wang Yunjian, Weiguo Li, Wenxiang Qian,
Wenxuan Wu, Yajun Wu, Yiding Zhou, Yingya Han, Yu Wenjun and Yuan Wang.

Below is the number of commits per employer (with authors count):
	242     Intel (53)
	209     Marvell (26)
	184     NVIDIA (27)
	 61     Huawei (7)
	 29     Microsoft (2)
	 27     Broadcom (5)
	 26     Red Hat (4)
	 24     NXP (8)
	 23     Semihalf (4)
	 21     Weiguo Li (1)
	 16     OKTET Labs (1)
	 12     Trustnet (1)
	 10     Arm (5)

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:
	 41     Akhil Goyal <gakhil@marvell.com>
	 29     Bruce Richardson <bruce.richardson@intel.com>
	 26     Ferruh Yigit <ferruh.yigit@intel.com>
	 20     Ori Kam <orika@nvidia.com>
	 19     David Marchand <david.marchand@redhat.com>
	 16     Tyler Retzlaff <roretzla@linux.microsoft.com>
	 15     Viacheslav Ovsiienko <viacheslavo@nvidia.com>
	 15     Morten Brørup <mb@smartsharesystems.com>
	 15     Chenbo Xia <chenbo.xia@intel.com>
	 14     Stephen Hemminger <stephen@networkplumber.org>
	 14     Jerin Jacob <jerinj@marvell.com>
	 12     Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
	 11     Ruifeng Wang <ruifeng.wang@arm.com>
	 11     Maxime Coquelin <maxime.coquelin@redhat.com>


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

Thanks everyone



                 reply	other threads:[~2022-03-17  9:54 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=2392757.yKVeVyVuyW@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).