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.08 (2019 August)
- new device specification (devargs) syntax
- documentation for device management
- TCP SEQ, TCP ACK and GRE key matching with rte_flow API and mlx5 implementation
- setting metadata in RX, with rte_flow API and mlx5 implementation, and receiving it as part of mbuf
- mlx5 offload ICMP ping, IP-in-IP inner RSS, TCP flags matching, LRO and hairpin
- better mlx5 rte_flow_query rate and latency
- better mlx5 out of the box TX performance
- robustness additions in mlx5 data-path error handling and recovery
- initial support for Huawei Intelligent PCIe NIC
- ice PMD rte_flow, ethertype & tunnel filters and inner L3/L4 checksum strip/insertion support
- i40e PMD partial offload support
- rawdev IOAT (Intel QuickData Technology) PMD
- af_xdp PMD busy polling and zero copy (using external mbuf) support
- bbdev new 4G FEC PMD & add 5G FEC extension support
- power telemetry busyness report support
- cryptodev encrypted digest for 5G use-cases support
- cryptodev RSA API update
- sched library enhancements
- IPsec fragmented/multi-segment packets support
Version 19.11 (2019 November)
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: June 3, 2019
- Integration deadline: July 1, 2019
- Release: August 1, 2019
- Proposal deadline: September 6, 2019
- Integration deadline: October 11, 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 email@example.com only (avoiding firstname.lastname@example.org).
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|
|17.11.6||17.11.7||August 12, 2019||November 2019 (LTS)||Yongseok Koh|
|18.11.2||18.11.3||September 2019||November 2020 (LTS)||Kevin Traynor|
|-||19.05.1||September 2019||September 2019||?|
|-||19.08.1||December 2019||December 2019||?|
|-||19.11.1||March 2020||November 2021 (LTS)||Luca Boccassi|