DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: DPDK 24.07 released
Date: Wed, 31 Jul 2024 21:22:45 +0200	[thread overview]
Message-ID: <8529494.5OynTdThKG@thomas> (raw)

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

This is the work achieved during the last months:
	954 commits from 191 authors
	1631 files changed, 80005 insertions(+), 25069 deletions(-)


It is not planned to start a maintenance branch for 24.07.
This version is ABI-compatible with 23.11 and 24.03.

Below are some new features:
	- pointer compression library
	- SVE support in the hash library
	- FEC support in Intel i40e and ice
	- Intel E830 support in ice driver
	- Napatech ntnic driver initialization
	- AMD Pensando ionic crypto driver
	- UADK compress driver
	- Marvell Odyssey ODM DMA driver
	- log cleanups in drivers
	- more cleanups to prepare MSVC build

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


There are 49 new contributors (including authors, reviewers and testers).
Welcome to Adrian Pielech, Alessio Igor Bogani, Alex Chapman,
Alexander Skorichenko, Anthony Harivel, Aviraj CJ, Barbara Skobiej,
Chenming Chang, Daniel Gregory, Daniil Ushkov, Dean Marx, Eryk Rybak,
Francis Racicot, Haoqian He, Harjot Singh, Hongbo Li, Igor Gutorov,
Jan Sokolowski, Jedrzej Jagielski, Jiang Yu, Joel Kavanagh, Jun Wang,
Kiran Vedere, Mahmoud Maatuq, Marcin Jurczak, Marek Mical,
Marek Zalfresso-jundzillo, Michael Theodore Stolarchuk, Pabitra Dalai,
Pawel Sobczyk, Piotr Raczynski, Potnuri Bharat Teja,
Prathisna Padmasanan, Przemek Kitszel, Radoslaw Tyl, Remigiusz Konca,
Serhii Iliushyk, Shaiq Wani, Shreesh Adiga, Shuo Li, Soumyadeep Hore,
Sriram Yagnaraman, Tathagat Priyadarshi, Tomasz Wakula, Varun Sethi,
Vipin Padmam Ramesh, Waldemar Dworakowski, Yoan Picchi, Yochai Hagvi, 
and Yuan Zhiyuan.


Below is the number of commits per employer (with authors count):
	247     Intel (77)
	135     NVIDIA (23)
	111     Corigine (5)
	 91     Marvell (18)
	 54     Red Hat (5)
	 46     AMD (5)
	 40     Arm (5)
	 39     networkplumber.org (1)
	 36     Microsoft (3)
	 23     NXP (7)
	 22     Napatech (2)
	 21     Trustnet (1)
	 18     Huawei (5)
	 15     Amazon (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:
	 35     Morten Brørup <mb@smartsharesystems.com>
	 27     Juraj Linkeš <juraj.linkes@pantheon.tech>
	 25     Ferruh Yigit <ferruh.yigit@amd.com>
	 24     Jeremy Spewock <jspewock@iol.unh.edu>
	 24     Akhil Goyal <gakhil@marvell.com>
	 22     Paul Szczepanek <paul.szczepanek@arm.com>
	 19     Bruce Richardson <bruce.richardson@intel.com>
	 18     Stephen Hemminger <stephen@networkplumber.org>


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


Don't forget to register for the DPDK Summit in September:
	https://events.linuxfoundation.org/dpdk-summit/

Thanks everyone, see you in Montreal



                 reply	other threads:[~2024-07-31 19:22 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=8529494.5OynTdThKG@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).