From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] DPDK 19.05 released
Date: Tue, 14 May 2019 03:05:12 +0200 [thread overview]
Message-ID: <5046677.2mBT3sk3aR@xps> (raw)
A new major release is available:
https://fast.dpdk.org/rel/dpdk-19.05.tar.xz
The statistics:
1056 commits from 142 authors
1605 files changed, 78822 insertions(+), 27754 deletions(-)
Below are some new features, grouped by category.
General:
- helloworld on Windows
- RCU library
- C11 memory ordering in spinlock, rwlock and new ticketlock
- lock-free extendable bucket in hash library
- stack library and lock-free stack mempool handler
- DMA mapping for external memory
Networking:
- min/max MTU info
- iterators for multi-ports device
- AF_XDP PMD
- Netcope FPGA NFB PMD
- Intel FPGA ipn3ke PMD
- Intel FPGA ifc vDPA
- Intel ice vectorized
- Mellanox large scale mlx5 flow engine
- failsafe/mlx4 in secondary process
- Aquantia atlantic MACsec
Cryptography:
- more algorithms in IPsec library
- Intel qat asymmetric crypto
Applications:
- live testpmd statistics
- testpmd optimizations
More details in the release notes:
http://doc.dpdk.org/guides/rel_notes/release_19_05.html
There are 46 new contributors (including authors, reviewers and testers).
Thanks to Akeem G Abodunrin, Andrey Nikolaev, Andrius Sirvys,
Ankur Dwivedi, Archana Muniganti, Bruce Allan, Chenbo Xia,
Chinh T Cao, Dan Nowlin, Dan Wei, Davide Caratti, Eduard Serra,
Harini Ramakrishnan, Hui Zhao, Jakub Grajciar, Jie Pan, Krzysztof Kanas,
Li Qiang, Liang Zhang, Linfan, Marcin Hajkowski, Marcin Smoczynski,
Mark Gillott, Matthew Vick, Michael Santana, Minghuan Lian,
Natanael Copa, Oleg Polyakov, Pablo Cascón, Pallavi Kadam,
Paul E. McKenney, Paul Greenwalt, Peng Huang, Peng Yuan, Qimai Xiao,
Ranjit Menon, Rastislav Cernay, Simei Su, Tejasree Kondoj, Victor Raj,
Vignesh Sridhar, Vishal Kulkarni, Wenjie Sun, Yi Liu, Ying A Wang and
Yufeng Mo.
Below is the number of patches per company (with authors count):
442 Intel (63)
158 Mellanox (8)
57 Marvell (9)
55 NXP (7)
53 Solarflare (4)
50 RedHat (8)
49 Microsoft (2)
38 OKTET Labs (2)
26 Aquantia (2)
26 ARM (6)
20 Cisco (3)
Based on Reviewed-by and Acked-by tags, the top reviewers are:
74 Ferruh Yigit <ferruh.yigit@intel.com>
70 Shahaf Shuler <shahafs@mellanox.com>
45 Rami Rosen <ramirose@gmail.com>
42 Qiming Yang <qiming.yang@intel.com>
41 Wenzhuo Lu <wenzhuo.lu@intel.com>
41 Maxime Coquelin <maxime.coquelin@redhat.com>
39 Akhil Goyal <akhil.goyal@nxp.com>
35 Qi Zhang <qi.z.zhang@intel.com>
32 Luca Boccassi <bluca@debian.org>
32 Anatoly Burakov <anatoly.burakov@intel.com>
30 Konstantin Ananyev <konstantin.ananyev@intel.com>
30 Fiona Trahe <fiona.trahe@intel.com>
26 Bruce Richardson <bruce.richardson@intel.com>
24 Yongseok Koh <yskoh@mellanox.com>
23 David Marchand <david.marchand@redhat.com>
21 John McNamara <john.mcnamara@intel.com>
20 Jerin Jacob <jerinj@marvell.com>
The new features for 19.08 may be submitted during the next three weeks,
in order to be reviewed and integrated during June.
DPDK 19.08 should be released at the very beginning of August.
http://core.dpdk.org/roadmap#dates
Thanks everyone
PS: in June do not miss Asian events in China and Japan
next reply other threads:[~2019-05-14 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 1:05 Thomas Monjalon [this message]
2019-05-14 1:05 ` 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=5046677.2mBT3sk3aR@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).