From: "St Leger, Jim" <jim.st.leger@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 21.08 released
Date: Sun, 8 Aug 2021 17:50:58 +0000 [thread overview]
Message-ID: <AEA3C384-E361-4855-AA88-230A19DD1445@intel.com> (raw)
In-Reply-To: <2753027.Nt7CRkRa4j@thomas>
Nice work by all! (This release should be called the Olympic Release, out just as the Tokyo 2020 games are concluding.)
Now go off and enjoy some well-earned summer holidays.
Stay safe,
Jim
> On Aug 8, 2021, at 10:47, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> A new release is available:
> https://fast.dpdk.org/rel/dpdk-21.08.tar.xz
>
> Summer release numbers:
> 922 commits from 159 authors
> 1069 files changed, 150746 insertions(+), 85146 deletions(-)
>
> It is not planned to start a maintenance branch for 21.08.
> This version is ABI-compatible with 20.11, 21.02 and 21.05.
>
> Below are some new features:
> - Linux auxiliary bus
> - Aarch32 cross-compilation
> - Arm CPPC power management
> - Rx multi-queue monitoring for power management
> - XZ compressed firmware read
> - Marvell CNXK drivers for ethernet, crypto and baseband PHY
> - Wangxun ngbe ethernet driver
> - NVIDIA mlx5 crypto driver supporting AES-XTS
> - ISAL compress support on Arm
>
> More details in the release notes:
> https://doc.dpdk.org/guides/rel_notes/release_21_08.html
>
>
> There are 30 new contributors (including authors, reviewers and testers).
> Welcome to Aakash Sasidharan, Aman Deep Singh, Cheng Liu, Chenglian Sun,
> Conor Fogarty, Douglas Flint, Gaoxiang Liu, Ghalem Boudour,
> Gordon Noonan, Heng Wang, Henry Nadeau, James Grant, Jeffrey Huang,
> Jochen Behrens, John Levon, Lior Margalit, Martin Havlik,
> Naga Harish K S V, Nathan Skrzypczak, Owen Hilyard, Paulis Gributs,
> Raja Zidane, Rebecca Troy, Rob Scheepens, Rongwei Liu, Shai Brandes,
> Srujana Challa, Tudor Cornea, Vanshika Shukla, and Yixue Wang.
>
> Below is the number of commits per employer (with authors count):
> 222 Marvell (22)
> 183 NVIDIA (26)
> 168 Intel (44)
> 100 Broadcom (12)
> 45 OKTET Labs (5)
> 36 Huawei (7)
> 35 Arm (7)
> 29 Red Hat (5)
> 20 Trustnet (1)
> 17 6WIND (3)
> 13 Microsoft (2)
> 8 NXP (4)
> 7 Semihalf (1)
> 5 UNH (2)
> 5 PANTHEON.tech (1)
> 4 Chelsio (1)
> 3 IBM (1)
>
> Based on Reviewed-by and Acked-by tags, the top non-PMD reviewers are:
> 45 Akhil Goyal <gakhil@marvell.com>
> 34 Jerin Jacob <jerinj@marvell.com>
> 21 Ruifeng Wang <ruifeng.wang@arm.com>
> 20 Ajit Khaparde <ajit.khaparde@broadcom.com>
> 19 Matan Azrad <matan@nvidia.com>
> 19 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> 17 Konstantin Ananyev <konstantin.ananyev@intel.com>
> 15 Chenbo Xia <chenbo.xia@intel.com>
> 14 Maxime Coquelin <maxime.coquelin@redhat.com>
> 14 David Marchand <david.marchand@redhat.com>
> 13 Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> 11 Thomas Monjalon <thomas@monjalon.net>
> 9 Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> 8 Stephen Hemminger <stephen@networkplumber.org>
> 8 Bruce Richardson <bruce.richardson@intel.com>
>
>
> DPDK 21.11 will be a big and busy release.
> The new features for 21.11 can be submitted during one month:
> http://core.dpdk.org/roadmap#dates
> Please share your features roadmap.
>
> Thanks everyone
>
>
prev parent reply other threads:[~2021-08-08 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 17:46 Thomas Monjalon
2021-08-08 17:50 ` St Leger, Jim [this message]
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=AEA3C384-E361-4855-AA88-230A19DD1445@intel.com \
--to=jim.st.leger@intel.com \
--cc=dev@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).