1 ABI and API Deprecation
2 =======================
4 See the :doc:`guidelines document for details of the ABI policy </contributing/versioning>`.
5 API and ABI deprecation notices are to be posted here.
11 * Significant ABI changes are planned for struct rte_eth_dev to support up to
12 1024 queues per port. This change will be in release 2.2.
13 There is no backward compatibility planned from release 2.2.
14 All binaries will need to be rebuilt from release 2.2.
16 * The Macros RTE_HASH_BUCKET_ENTRIES_MAX and RTE_HASH_KEY_LENGTH_MAX are
17 deprecated and will be removed with version 2.2.
19 * The function rte_jhash2 is deprecated and should be removed.
21 * The following fields have been deprecated in rte_eth_stats:
22 imissed, ibadcrc, ibadlen, imcasts, fdirmatch, fdirmiss,
23 tx_pause_xon, rx_pause_xon, tx_pause_xoff, rx_pause_xoff
25 * API for flow director filters has been replaced by rte_eth_dev_filter_ctrl.
26 Following old API is deprecated and will be removed with version 2.2 without
27 backward compatibility.
28 Functions: rte_eth_dev_fdir_*.
29 Structures: rte_fdir_*, rte_eth_fdir.
30 Enums: rte_l4type, rte_iptype.
32 * ABI changes are planned for struct rte_eth_fdir_flow_ext in order to support
33 flow director filtering in VF. The release 2.1 does not contain these ABI
34 changes, but release 2.2 will, and no backwards compatibility is planned.
36 * ABI changes are planned for struct rte_eth_fdir_filter and
37 rte_eth_fdir_masks in order to support new flow director modes,
38 MAC VLAN and Cloud, on x550. The MAC VLAN mode means the MAC and
39 VLAN are monitored. The Cloud mode is for VxLAN and NVGRE, and
40 the tunnel type, TNI/VNI, inner MAC and inner VLAN are monitored.
41 The release 2.2 will contain these changes without backwards compatibility.
43 * librte_pmd_ring: The deprecated functions rte_eth_ring_pair_create and
44 rte_eth_ring_pair_attach should be removed.
46 * ABI changes are planned for struct virtio_net in order to support vhost-user
47 multiple queues feature.
48 It should be integrated in release 2.2 without backward compatibility.
50 * The scheduler hierarchy structure (rte_sched_port_hierarchy) will change to
51 allow for a larger number of subport entries.
52 The number of available traffic_classes and queues may also change.
53 The mbuf structure element for sched hierarchy will also change from a single
54 32 bit to a 64 bit structure.
56 * The scheduler statistics structure will change to allow keeping track of
59 * librte_cfgfile: In order to allow for longer names and values,
60 the value of macros CFG_NAME_LEN and CFG_NAME_VAL will be increased.
61 Most likely, the new values will be 64 and 256, respectively.
63 * librte_port: Macros to access the packet meta-data stored within the
64 packet buffer will be adjusted to cover the packet mbuf structure as well,
65 as currently they are able to access any packet buffer location except the
66 packet mbuf structure.
68 * librte_table LPM: A new parameter to hold the table name will be added to
69 the LPM table parameter structure.
71 * librte_table: New functions for table entry bulk add/delete will be added
72 to the table operations structure.
74 * librte_table hash: Key mask parameter will be added to the hash table
75 parameter structure for 8-byte key and 16-byte key extendible bucket and
78 * librte_pipeline: The prototype for the pipeline input port, output port
79 and table action handlers will be updated:
80 the pipeline parameter will be added, the packets mask parameter will be
81 either removed (for input port action handler) or made input-only.