From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] DPDK 20.11 released
Date: Fri, 27 Nov 2020 22:37:48 +0100 [thread overview]
Message-ID: <7762693.GJoe4xxER1@thomas> (raw)
A new major release is available:
https://fast.dpdk.org/rel/dpdk-20.11.tar.xz
Our Thanksgiving gift is the biggest DPDK release ever:
2195 commits from 214 authors
2665 files changed, 269546 insertions(+), 107426 deletions(-)
The branch 20.11 should be supported for at least two years,
making it recommended for system integration and deployment.
The maintainer of this new LTS is Kevin Traynor.
The new major ABI version is 21.
The next releases 21.02, 21.05 and 21.08 will be ABI compatible with 20.11.
Below are some new features, grouped by category.
* General
- mbuf dynamic area increased from 16 to 36 bytes
- ring zero copy
- SIMD bitwidth limit API
- Windows PCI netuio
- moved igb_uio to dpdk-kmods/linux
- removed Python 2 support
- removed Make support
* Networking
- FEC API
- Rx buffer split
- thread safety in flow API
- shared action in flow API
- flow sampling and mirroring
- tunnel offload API
- multi-port hairpin
- Solarflare EF100 architecture
- Wangxun txgbe driver
- vhost-vDPA backend in virtio-user
- removed vhost dequeue zero-copy
- removed legacy ethdev filtering
- SWX pipeline aligned with P4
* Baseband
- Intel ACC100 driver
* Cryptography
- raw datapath API
- Broadcom BCMFS symmetric crypto driver
* RegEx
- Marvell OCTEON TX2 regex driver
* Others
- Intel DLB/DLB2 drivers
- Intel DSA support in IOAT driver
More details in the release notes:
https://doc.dpdk.org/guides/rel_notes/release_20_11.html
There are 64 new contributors (including authors, reviewers and testers).
Welcome to Aidan Goddard, Amit Bernstein, Andrey Vesnovaty, Artur Rojek,
Benoît Ganne, Brandon Lo, Brian Johnson, Brian Poole, Christophe Grosse,
Churchill Khangar, Conor Walsh, David Liu, Dawid Lukwinski,
Diogo Behrens, Dongdong Liu, Franck Lenormand, Galazka Krzysztof,
Guoyang Zhou, Haggai Eran, Harshitha Ramamurthy, Ibtisam Tariq,
Ido Segev, Jay Jayatheerthan, Jiawen Wu, Jie Zhou, John Alexander,
Julien Massonneau, Jørgen Østergaard Sloth, Khoa To, Li Zhang,
Lingli Chen, Liu Tianjiao, Maciej Rabeda, Marcel Cornu, Mike Ximing Chen,
Muthurajan Jayakumar, Nan Chen, Nick Connolly, Norbert Ciosek,
Omkar Maslekar, Padraig Connolly, Piotr Bronowski, Przemyslaw Ciesielski,
Qin Sun, Radha Mohan Chintakuntla, Rani Sharoni, Raveendra Padasalagi,
Robin Zhang, RongQing Li, Shay Amir, Steve Yang, Steven Lariau, Tom Rix,
Venkata Suresh Kumar P, Vijay Kumar Srivastava, Vikas Gupta,
Vimal Chungath, Vipul Ashri, Wei Huang, Wei Ling, Weqaar Janjua, Yi Yang,
Yogesh Jangra and Zhenghua Zhou.
Below is the number of commits per employer (with authors count):
687 Intel (72)
439 Nvidia (34)
150 Huawei (11)
123 Broadcom (15)
116 Solarflare (1)
104 Red Hat (6)
96 OKTET Labs (3)
79 Marvell (16)
71 Arm (7)
59 Trustnet (1)
52 Microsoft (3)
51 NXP (12)
27 Semihalf (1)
27 Samsung (2)
19 6WIND (5)
17 Cisco (4)
13 BIFIT (1)
11 Emumba (2)
7 Xilinx (1)
7 Chelsio (2)
5 Inspur (1)
4 MayaData (1)
Based on Reviewed-by and Acked-by tags, the top non-PMD reviewers are:
128 Ferruh Yigit <ferruh.yigit@intel.com>
68 Bruce Richardson <bruce.richardson@intel.com>
63 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
62 David Marchand <david.marchand@redhat.com>
53 Ruifeng Wang <ruifeng.wang@arm.com>
40 Konstantin Ananyev <konstantin.ananyev@intel.com>
38 Ajit Khaparde <ajit.khaparde@broadcom.com>
37 Ori Kam <orika@nvidia.com>
33 Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
The new features for 21.02 may be submitted during the next 3 weeks,
in order to be reviewed and integrated before mid-January.
DPDK 21.02 should be small in order to release in early February:
https://core.dpdk.org/roadmap#dates
Please share your roadmap.
Thanks everyone, enjoy a well deserved rest.
reply other threads:[~2020-11-27 21:38 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=7762693.GJoe4xxER1@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).