1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright 2018 The DPDK contributors 3 4ABI and API Deprecation 5======================= 6 7See the :doc:`guidelines document for details of the ABI policy </contributing/versioning>`. 8API and ABI deprecation notices are to be posted here. 9 10 11Deprecation Notices 12------------------- 13 14* meson: The minimum supported version of meson for configuring and building 15 DPDK will be increased to v0.47.1 (from 0.41) from DPDK 19.05 onwards. For 16 those users with a version earlier than 0.47.1, an updated copy of meson 17 can be got using the ``pip``, or ``pip3``, tool for downloading python 18 packages. 19 20* kvargs: The function ``rte_kvargs_process`` will get a new parameter 21 for returning key match count. It will ease handling of no-match case. 22 23* eal: both declaring and identifying devices will be streamlined in v18.11. 24 New functions will appear to query a specific port from buses, classes of 25 device and device drivers. Device declaration will be made coherent with the 26 new scheme of device identification. 27 As such, ``rte_devargs`` device representation will change. 28 29 - The enum ``rte_devtype`` was used to identify a bus and will disappear. 30 - Functions previously deprecated will change or disappear: 31 32 + ``rte_eal_devargs_type_count`` 33 34* vfio: removal of ``rte_vfio_dma_map`` and ``rte_vfio_dma_unmap`` APIs which 35 have been replaced with ``rte_dev_dma_map`` and ``rte_dev_dma_unmap`` 36 functions. The due date for the removal targets DPDK 20.02. 37 38* pci: Several exposed functions are misnamed. 39 The following functions are deprecated starting from v17.11 and are replaced: 40 41 - ``eal_parse_pci_BDF`` replaced by ``rte_pci_addr_parse`` 42 - ``eal_parse_pci_DomBDF`` replaced by ``rte_pci_addr_parse`` 43 - ``rte_eal_compare_pci_addr`` replaced by ``rte_pci_addr_cmp`` 44 45* dpaa2: removal of ``rte_dpaa2_memsegs`` structure which has been replaced 46 by a pa-va search library. This structure was earlier being used for holding 47 memory segments used by dpaa2 driver for faster pa->va translation. This 48 structure would be made internal (or removed if all dependencies are cleared) 49 in future releases. 50 51* ethdev: the legacy filter API, including 52 ``rte_eth_dev_filter_supported()``, ``rte_eth_dev_filter_ctrl()`` as well 53 as filter types MACVLAN, ETHERTYPE, FLEXIBLE, SYN, NTUPLE, TUNNEL, FDIR, 54 HASH and L2_TUNNEL, is superseded by the generic flow API (rte_flow) in 55 PMDs that implement the latter. 56 Target release for removal of the legacy API will be defined once most 57 PMDs have switched to rte_flow. 58 59* kni: remove KNI ethtool support. To clarify, this is not to remove the KNI, 60 but only to remove ethtool support of it that is disabled by default and 61 can be enabled via ``CONFIG_RTE_KNI_KMOD_ETHTOOL`` config option. 62 Existing KNI ethtool implementation is only supported by ``igb`` & ``ixgbe`` 63 drivers, by using a copy of kernel drivers in DPDK. This model cannot be 64 extended to all drivers in DPDK and it is too much effort to maintain 65 kernel modules in DPDK. As a result users won't be able to use ``ethtool`` 66 via ``igb`` & ``ixgbe`` anymore. 67 68* meter: New ``rte_color`` definition will be added in 19.02 and that will 69 replace ``enum rte_meter_color`` in meter library in 19.05. This will help 70 to consolidate color definition, which is currently replicated in many places, 71 such as: rte_meter.h, rte_mtr.h, rte_tm.h. 72 73* crypto/aesni_mb: the minimum supported intel-ipsec-mb library version will be 74 changed from 0.49.0 to 0.52.0. 75 76* cryptodev: New member in ``rte_cryptodev_config`` to allow applications to 77 disable features supported by the crypto device. Only the following features 78 would be allowed to be disabled this way, 79 80 - ``RTE_CRYPTODEV_FF_SYMMETRIC_CRYPTO`` 81 - ``RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO`` 82 - ``RTE_CRYPTODEV_FF_SECURITY`` 83 84 Disabling unused features would facilitate efficient usage of HW/SW offload. 85 86 - Member ``uint64_t ff_disable`` in ``rte_cryptodev_config`` 87 88 The field would be added in v19.08. 89