From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] DPDK 20.02 released
Date: Tue, 25 Feb 2020 23:59:52 +0100 [thread overview]
Message-ID: <1894223.0S5aU1g85B@xps> (raw)
A new release is available:
https://fast.dpdk.org/rel/dpdk-20.02.tar.xz
The statistics looks like a post-LTS ABI-compatible release:
820 commits from 156 authors
876 files changed, 59941 insertions(+), 22565 deletions(-)
It is not planned (yet) to start a maintenance branch for 20.02.
This release and next ones (20.05, 20.08) are ABI-compatible with 19.11.
Below are some new features, grouped by category.
General:
- ABI check tooling
- FreeBSD 13 support
- Linux kernel modules disabled in default build
- API wait until equal
- use CPU lcore with ID > total max
- ring with configurable element size
- pool of mbufs with pinned external buffers
Networking:
- Pensando ionic driver
- Marvell driver for OCTEON TX2 end point
- Mellanox vDPA driver
- rte_flow API for DSCP
- rte_flow API for L2TPv3 over IP
Cryptography:
- Marvell OCTEON TX2 inline IPsec
- CPU crypto based on new libraries (intel-ipsec-mb and AArch64cryptolib)
- synchronous CPU crypto API
- more algorithms: ECDSA, ECPM
Applications:
- event mode in l3fwd example
More details in the release notes:
http://doc.dpdk.org/guides/rel_notes/release_20_02.html
There are 69 new contributors (including authors, reviewers and testers).
Welcome to Abed Kamaluddin, Abhishek Marathe, Adam Ludkiewicz,
Adrian Podlawski, Aleksandr Loktionov, Alexander Kozyrev,
Alfredo Cardigliano, Andrew Pinski, Apeksha Gupta,
Balakrishna Bhamidipati, Carolyn Wyborny, Chandu Babu N,
Cheng Jiang, Chengchang Tang, Damian Milosek, Dariusz Chaberski,
Dariusz Jagus, Dexuan Cui, Dmitry Kozlyuk, Donald Lee, Dzmitry Sautsa,
Eugenio Pérez, Fang TongHao, Gal Cohen, Gargi Sau, Girish Nandibasappa,
Ilja Van Sprundel, Itsuro Oda, Jaroslaw Gawin, Jörg Thalheim,
Kiran Patil, Krzysztof Galazka, Kumar Amber, Li Feng, Lijun Ou,
Mahipal Challa, Manish Chopra, Marcin Formela, Martyna Szapar,
Mateusz Rusinski, Michael Baum, Michal Litwicki, Michal Swiatkowski,
Narcisa Vasile, Niclas Storm, Pandi Kumar Maharajan, Piotr Azarewicz,
Piotr Kwapulinski, Piotr Pietruszewski, Prateek Agarwal, Praveen Shetty,
Rafael Ávila de Espíndola, Ricardo Roldan, Robert Konklewski,
Satananda Burla, Savinay Dharmappa, Scott Wasson, Selwin Sebastian,
Shannon Nelson, Shiri Kuzin, Sunil Pai G, Sylwia Wnuczko, Thomas Faivre,
Tomasz Konieczny, Vitaliy Mysak, Xuan Ding, Xuan Li, Xueming Zhang,
and Yisen Zhuang.
Below is the number of patches per company (with authors count):
268 Intel (54)
193 Mellanox (16)
114 Marvell (23)
49 Broadcom (7)
34 Red Hat (7)
32 Huawei (8)
30 ARM (4)
25 Microsoft (1)
18 ntop (1)
9 6WIND (5)
6 NXP (4)
5 AMD (3)
4 VA Linux Systems (1)
4 Ericsson (1)
4 Cisco (1)
Based on Reviewed-by and Acked-by tags, the top reviewers are:
76 Viacheslav Ovsiienko <viacheslavo@mellanox.com>
56 Qi Zhang <qi.z.zhang@intel.com>
47 Xiaolong Ye <xiaolong.ye@intel.com>
46 Akhil Goyal <akhil.goyal@nxp.com>
44 Ferruh Yigit <ferruh.yigit@intel.com>
43 Matan Azrad <matan@mellanox.com>
43 Jerin Jacob <jerinj@marvell.com>
38 Beilei Xing <beilei.xing@intel.com>
35 Qiming Yang <qiming.yang@intel.com>
34 Ajit Khaparde <ajit.khaparde@broadcom.com>
33 Maxime Coquelin <maxime.coquelin@redhat.com>
31 Ori Kam <orika@mellanox.com>
25 Gavin Hu <gavin.hu@arm.com>
24 David Marchand <david.marchand@redhat.com>
23 Konstantin Ananyev <konstantin.ananyev@intel.com>
The new features for 20.05 may be submitted during the next 21 days,
in order to be reviewed and integrated before mid-April.
DPDK 20.05 should be released on 20-05-20.
http://core.dpdk.org/roadmap#dates
The schedule is pushed because of the special worldwide context.
Some future release cycles will have to be shorter.
Thanks everyone, and take care.
reply other threads:[~2020-02-25 23:00 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=1894223.0S5aU1g85B@xps \
--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).