Major known features and milestones may be noted here. This is not a commitment but plan of work. This list is obviously neither complete nor guaranteed.
Version 19.05 (2019 May)
- initial support for DPDK on Windows
- new device specification (devargs) syntax
- documentation for device management
- DMA mapping API for external memory
- relaxed memory ordering in spinlock and rwlock
- RCU library
- lock-free extended bucket in hash library
- TCP SEQ and ACK offload with rte_flow API and mlx5 implementation
- ICMP ping offload with rte_flow API and mlx5 implementation
- new mlx5 steering flow engine for high (millions/sec) insertion rate
- mlx5 out of the box performance improvements
- mlx5/mlx4 robustness improvement for Rx/Tx errors
- failsafe support in multi-process
- AF_XDP PMD
- baseband device turbo PMD
- QAT compression PMD support for large scatter-gather lists
- QAT asymmetric crypto with support for modexp and modinv
- additional crypto/auth algorithms in the IPsec library
Version 19.08 (2019 August)
- initial support for Huawei Intelligent PCIe NIC
Version 19.11 (2019 September)
Nice to have - Future
- multi-process rework
- automatic UIO/VFIO binding
- infiniband driver class (ibdev)
- default configuration from files
- generic white/blacklisting
- libedit integration
A typical release should be done after 3 months.
It is designed to allow DPDK to keep evolving at a rapid pace while giving enough opportunity to review, discuss and improve the contributions.
The merge window will open once the previous release is complete. First version of a new feature must be submitted before the proposal deadline. Features that miss this first period will be deferred until the next release.
Updated versions of patches (v2, v3, etc.) will be submitted to address comments. The new features must be properly reviewed, tested and accepted before the integration deadline. Otherwise, they will be postponed to the next releases.
At the end of the merge window, the first release candidate is out.
The last period is 1 month long and is dedicated to bug fixing.
- Proposal deadline: March 1, 2019
- Integration deadline: March 29, 2019
- Release: May 10, 2019
- Release: August 2, 2019
- Release: November 8, 2019
There is a documentation page describing the guidelines of the stable releases.
Stable point releases follow mainline releases.
After each -rc tag and after the final version, relevant bug fixes get backported by the stable maintainers into the respective branches in “bursts”.
Developers can provide stable-specific patches by sending them to firstname.lastname@example.org only (avoiding email@example.com).
After all the relevant bugfixes have been backported, regression tests are run, and if clear, the stable release is announced.
Typically a new stable release version follows a mainline release by 1-2 weeks, depending on the test results.
|Current version||Next version||Next version Date||End of life||Maintainer|
|16.11.9||-||-||March 2019 (LTS)||Luca Boccassi|
|17.11.5||17.11.6||March 29, 2019||November 2019 (LTS)||Yongseok Koh|
|18.02.2||-||-||June 2018||Luca Boccassi|
|18.05.1||-||-||August 2018||Christian Ehrhardt|
|-||18.08.1||November 16, 2018||November 2018||Kevin Traynor|
|-||18.11.1||February 15, 2019||November 2020 (LTS)||Kevin Traynor|
|-||19.02.1||May 31, 2019||June 2019||?|
|-||19.05.1||August 16, 2019||September 2019||?|
|-||19.08.1||November 29, 2019||December 2019||?|