Roadmap

Version 24.11 (2024 November)

• AMD uncore power
• non-temporal memory copy
• mempool cache zero-copy get/put bulk
• memarea library
• ring generic implementation removal and C11 improvement
• PMU counter for self monitoring/profiling
• VFIO cdev/iommufd
• ethdev flow action jump to table index
• axgbe TSO
• cpfl flow offload with P4
• dpaa IEEE 1588 PTP
• dpaa offline (O/H) port
• dpaa2 flow offload enhancements
• ena LLQ policy refactor
• ena dynamic HRSS size
• ena asynchronous reset request from device
• enetc NXP driver version 4
• eqos NXP driver
• i40e/ice/iavf MDD debug
• idpf AVX2
• mlx5 hairpin statistics
• mlx5 non-template flow using template async engine
• rnp driver from Mucse
• sssnic driver from 3SNIC
• xsc Yunsilicon driver
• virtio hash reporting
• vhost small copy with CPU in DSA-accelerated vhost
• vhost port mirroring with DMAdev
• testpmd attach/detach on primary and secondary
• cryptodev EdDSA asymmetric algorithm
• cryptodev EC refactoring
• PDCP control PDU
• mldev support of mbuf
• eventdev power optimization
• eventdev adapter for mldev
• dlb2 control and Rx adapter enhancements
• DTS ethdev test suites
• DTS automated documentation

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

Cycle model

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.

Scheduling

24.11

• Proposal deadline (RFC/v1 patches): 7 September 2024
• API freeze (-rc1): 7 October 2024
• PMD features freeze (-rc2): 28 October 2024
• Builtin applications features freeze (-rc3): 4 November 2024
• Release: 20 November 2024

Stable Releases

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 stable@dpdk.org only (avoiding dev@dpdk.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.