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 22.11 (2022 November)
- index-based per core mempool cache
- direct-rearm of Rx side buffers
- Tx QoS marking API
- protocol-based header split
- ethdev flow rules pre-configuration flags
- ethdev queue-based ageing event info
- pipeline connection tracking improvements
- AVF software back-end driver with device emulation libraries
- bonding Tx prepare
- octeontx2 mirroring
- qede initial support for next generation hardware
- qede flow API support
- spnic driver for Ramaxel devices
- ice header split
- idpf PMD for Intel IPU SoC
- Intel AFU PMD based on rawdev
- mlx5 flow matching of all switch ports in one rule
- vhost small copy with CPU in DSA-accelerated vhost
- virtio hash reporting
- more info in dpdk-proc-info
- qat with OpenSSL-3.0 library
- qat without dependency on OpenSSL-1.x
- event vector support in SW Rx eventdev adapter
- control adapter and RX adapter enhancements in DLB driver
- DLB assignment of SW/HW credit quanta on port usage hint
Nice to have - Future
- lock-free l3fwd algorithms
- multi-process rework
- automatic UIO/VFIO binding
- infiniband driver class (ibdev)
- default configuration from files
- generic allow/blocklisting
- libedit integration
- UBSan in build
- regex driver based on libpcre
- IF proxy
- performance test for IP reassembly
- IPv6 in lookaside IPsec example
- anti-replay in inline IPsec example
A typical release should be done after 4 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 windows, the first release candidates are out.
The last period is approximately 1 month long and is dedicated to bug fixing.
- Proposal deadline (RFC/v1 patches): 14 August 2022
- API freeze (-rc1): 3 October 2022
- PMD features freeze (-rc2): 24 October 2022
- Builtin applications features freeze (-rc3): 31 October 2022
- Release: 16 November 2022
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). Further information on subject prefixes for this case is documented here.
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 3-6 weeks, depending on the test results.
|Current version||Next version||Next version Date||End of life||Maintainers|
|18.11.11||-||-||December 2020 (EOL)||-|
|19.11.13||19.11.14||December 2022||December 2022 (LTS)||Christian Ehrhardt|
|20.11.6||20.11.7||December 2022||December 2022 (LTS)||Luca Boccassi, Xueming Li|
|21.11.2||21.11.3||December 2022||November 2023 (LTS)||Kevin Traynor|