DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] DPDK 17.11 released
Date: Wed, 15 Nov 2017 18:26:15 +0100	[thread overview]
Message-ID: <4165682.FMfjCqaZ3l@xps> (raw)

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

Some highlights:
	- IOVA awareness
	- PCI and VDEV buses moved to drivers
	- ethdev port id increased to 16 bits
	- ethdev Rx/Tx offload API reworked
	- Rx offload API for traffic metering and policing (rte_mtr)
	- IPsec offload API (rte_security)
	- Marvell Armada drivers
	- NXP DPAA1 drivers
	- Cavium OcteonTX drivers
	- NXP and Cavium implementations of event/Rx adapter
	- Netronome PF driver
	- Mellanox drivers reworked for upstream ibverbs support
	- SoftNIC driver for traffic management software fallback
	- vhost IOMMU
	- GSO library
	- flow classify library
	- membership library
	- power management updated
	- pipeline improvements
	- example app for service cores
	- example app and how-to for rte_flow API
	- Xen dom0 removed

More details in the release notes:
	http://dpdk.org/doc/guides/rel_notes/release_17_11.html

It is (again) the biggest DPDK release ever:
	1376 patches from 141 authors
	1279 files changed, 126273 insertions(+), 53732 deletions(-)

There are 55 new contributors
(including authors, reviewers and testers):
Thanks to Abhinandan Gujjar, Alexander Solganik, Alok Makhariya,
Ashish Jain, Aviad Yehezkel, Billy O'Mahony, Bing Zhao, Brian Brooks, 
Congwen Zhang, Edward Makarov, Eelco Chaudron, Elza Mathew, Forrest Shi, 
Ganghui Zeng, Haiying Wang, Ilia Kurakin, Intiyaz Basha, Jacek Siuda, 
Jay Zhou, Jia He, Jianwei Ma, Jie Liu, Job Abraham, Jonas Pfefferle, 
Lee Daly, Li Han, Lijuan Tu, Lukasz Majczak, Maria Lingemark, 
Marko Kovacevic, Nemanja Marjanovic, Omri Mor, Ophir Munk, Ori Kam, 
Pavan Bhagavatula, Pavan Nikhilesh, Pavel Shirshov, Pengzhen Liu, 
Phil Yang, Radoslaw Biernacki, Rory Sexton, Sebastian Basierski, 
Seth Howell, Seán Harte, Somnath Kotur, Song Zhu, Stefan Baranoff, 
Steven Luong, Tim McDaniel, Tomasz Duszynski, Tonghao Zhang, 
Venkatesh Nuthula, Vladimir Kuramshin, Yi Yang and Yipeng Wang.

Below is the number of patches per company (accuracy not perfect):
	417     Intel (56)
	220     6WIND (5)
	186     Cavium (9)
	157     Mellanox (13)
	118     NXP (7)
	 52     Broadcom (2)
	 36     Netronome (1)
	 34     RedHat (3)
	 31     Semihalf (2)
	 14     Solarflare (2)
	 13     ZTE (4)
	 12     Microsoft (2)
	 12     AT&T (2)
	 11     Cisco (4)
	 10     OKTET Labs (1)
	  7     IBM (2)
	  6     ARM (4)
	  5     Linaro (2)
	  3     Huawei (3)

The new features for 18.02 must be submitted before the next month,
in order to be reviewed and integrated during December.
The next release is expected to happen at the very beginning of February.

If you are reading this announcement live in the DPDK summit,
please stand up and applaud all the contributors of the community.
Thanks everyone

                 reply	other threads:[~2017-11-15 17:26 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=4165682.FMfjCqaZ3l@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).