DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: DPDK 22.07 released
Date: Mon, 18 Jul 2022 01:03:43 +0200	[thread overview]
Message-ID: <2454423.Sgy9Pd6rRy@thomas> (raw)

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

This Summer release is quite small:
	1021 commits from 177 authors
	1149 files changed, 77256 insertions(+), 26288 deletions(-)

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

Below are some new features:
	- initial RISC-V support
	- sequence lock
	- protocol-based metering
	- Rx threshold event
	- SFP telemetry
	- async vhost improvements
	- vhost library statistics
	- vmxnet3 versions 5 & 6
	- ECDH crypto
	- eventdev runtime attributes
	- DMA device telemetry
	- SWX pipeline improvements
	- integration as Meson subproject

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

Note: GCC 12 may emit some warnings, some fixes are missing.


There are 44 new contributors (including authors, reviewers and testers).
Welcome to Abdullah Ömer Yamaç, Abhimanyu Saini, Bassam Zaid AlKilani,
Damodharam Ammepalli, Deepak Khandelwal, Diana Wang, Don Wallwork,
Duncan Bellamy, Ferdinand Thiessen, Fidaullah Noonari, Frank Zhao,
Hanumanth Pothula, Heinrich Schuchardt, Hernan Vargas, Jakub Wysocki,
Jin Liu, Jiri Slaby, Ke Zhang, Kent Wires, Marcin Danilewicz,
Michael Rossberg, Michal Mazurek, Mike Pattrick, Mingxia Liu,
Niklas Söderlund, Omar Awaysa, Peng Zhang, Quentin Armitage,
Richard Donkin, Romain Delhomel, Sam Grove, Spike Du, Subendu Santra,
Tianhao Chai, Veerasenareddy Burru, Walter Heymans, Weiyuan Li,
Wenjing Qiao, Xiangjun Meng, Xu Ting, Yinjun Zhang, Yong Xu,
Zhichao Zeng and Zhipeng Lu.

Below is the number of commits per employer (with authors count):
	299     Intel (56)
	224     Marvell (31)
	114     NVIDIA (22)
	 82     Huawei (7)
	 65     Red Hat (3)
	 35     NXP (4)
	 29     Microsoft (3)
	 26     Broadcom (5)
	 23     Semihalf (4)
	 20     Corigine (5)
	 18     Trustnet (1)
	        ...

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:
	 54     Akhil Goyal <gakhil@marvell.com>
	 52     Fan Zhang <roy.fan.zhang@intel.com>
	 42     Jerin Jacob <jerinj@marvell.com>
	 35     Chenbo Xia <chenbo.xia@intel.com>
	 34     Maxime Coquelin <maxime.coquelin@redhat.com>
	 28     Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
	 23     Matan Azrad <matan@nvidia.com>
	 21     Bruce Richardson <bruce.richardson@intel.com>
	 20     Qi Zhang <qi.z.zhang@intel.com>
	 20     Ferruh Yigit <ferruh.yigit@xilinx.com>
	 19     Morten Brørup <mb@smartsharesystems.com>
	 19     Anoob Joseph <anoobj@marvell.com>


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

Thanks everyone



             reply	other threads:[~2022-07-17 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 23:03 Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-17 23:00 Thomas Monjalon

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