43. ABI and API Deprecation
See the guidelines document for details of the ABI Policy.
With DPDK 23.11, there will be a new major ABI version: 24. This means that during the development of 23.11, new items may be added to structs or enums, even if those additions involve an ABI compatibility breakage.
Other API and ABI deprecation notices are to be posted below.
43.1. Deprecation Notices
kvargs: The function
rte_kvargs_processwill get a new parameter for returning key match count. It will ease handling of no-match case.eal: The
-c <coremask>commandline parameter is deprecated and will be removed in a future release. Use the-l <corelist>or--lcores=<corelist>parameters instead to specify the cores to be used when running a DPDK application.eal: The
-s <service-coremask>commandline parameter is deprecated and will be removed in a future release. Use the-S <service-corelist>parameter instead to specify the cores to be used for background services in DPDK.lib: will fix extending some enum/define breaking the ABI. There are multiple samples in DPDK that enum/define terminated with a
.*MAX.*value which is used by iterators, and arrays holding these values are sized with this.*MAX.*value. So extending this enum/define increases the.*MAX.*value which increases the size of the array and depending on how/where the array is used this may break the ABI.RTE_ETH_FLOW_MAXis one sample of the mentioned case, adding a new flow type will break the ABI because offlex_mask[RTE_ETH_FLOW_MAX]array usage in following public struct hierarchy:rte_eth_fdir_flex_conf -> rte_eth_fdir_conf -> rte_eth_conf (in the middle). Need to identify this kind of usages and fix in 20.11, otherwise this blocks us extending existing enum/define. One solution can be using a fixed size array instead of.*MAX.*value.net, ethdev: The flow item
RTE_FLOW_ITEM_TYPE_VXLAN_GPEis replaced withRTE_FLOW_ITEM_TYPE_VXLAN. The structrte_flow_item_vxlan_gpeand its maskrte_flow_item_vxlan_gpe_maskare replaced withrte_flow_item_vxlanandrte_flow_item_vxlan_mask. The flow itemRTE_FLOW_ITEM_TYPE_VXLAN_GPE, the structsrte_flow_item_vxlan_gpe,rte_flow_item_vxlan_gpe_mask, and the header structrte_vxlan_gpe_hdrwith the macroRTE_ETHER_VXLAN_GPE_HLENwill be removed in DPDK 25.11.ethdev: The flow API matching pattern structures,
struct rte_flow_item_*, should start with relevant protocol header structure from lib/net/. The individual protocol header fields and the protocol header struct may be kept together in a union as a first migration step. In future (target is DPDK 23.11), the protocol header fields will be cleaned and only protocol header struct will remain.These items are not compliant (not including struct from lib/net/):
rte_flow_item_ahrte_flow_item_e_tagrte_flow_item_geneverte_flow_item_geneve_optrte_flow_item_grerte_flow_item_icmp6rte_flow_item_icmp6_nd_narte_flow_item_icmp6_nd_nsrte_flow_item_icmp6_nd_optrte_flow_item_icmp6_nd_opt_sla_ethrte_flow_item_icmp6_nd_opt_tla_ethrte_flow_item_igmprte_flow_item_ipv6_extrte_flow_item_l2tpv3oiprte_flow_item_mplsrte_flow_item_nshrte_flow_item_nvgrerte_flow_item_pfcprte_flow_item_pppoerte_flow_item_pppoe_proto_id
ethdev: Flow actions
PFandVFhave been deprecated since DPDK 21.11 and are yet to be removed. That still has not happened because there are net drivers which support combined use of either actionPFor actionVFwith actionQUEUE, namely, i40e, ixgbe and txgbe (L2 tunnel rule). It is unclear whether it is acceptable to just drop support for such a complex use case, so maintainers of the said drivers should take a closer look at this and provide assistance.ethdev: Actions
OF_DEC_NW_TTL,SET_IPV4_SRC,SET_IPV4_DST,SET_IPV6_SRC,SET_IPV6_DST,SET_TP_SRC,SET_TP_DST,DEC_TTL,SET_TTL,SET_MAC_SRC,SET_MAC_DST,INC_TCP_SEQ,DEC_TCP_SEQ,INC_TCP_ACK,DEC_TCP_ACK,SET_IPV4_DSCP,SET_IPV6_DSCP,SET_TAG,SET_METAare marked as legacy and superseded by the genericRTE_FLOW_ACTION_TYPE_MODIFY_FIELD. The legacy actions should be removed onceMODIFY_FIELDalternative is implemented in drivers.ethdev: Starting in 26.11, the function
rte_eth_dev_get_name_by_port()will take a size parameter as well as the string buffer. This will detect and prevent accidental overwriting of caller provided buffer.bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in
drivers/bus/vmbus/rte_bus_vmbus.hwill become internal to DPDK. Those API functions are used internally by DPDK core and netvsc PMD.