* eal: The function ``rte_eal_remote_launch`` will return new error codes
after read or write error on the pipe, instead of calling ``rte_panic``.
-* eal: The ``rte_logs`` struct and global symbol will be made private to
- remove it from the externally visible ABI and allow it to be updated in the
- future.
-
-* eal: The ``rte_dev_event`` structure will be made private to the EAL as no
- public API makes use of it.
-
* rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
not allow for writing optimized code for all the CPU architectures supported
in DPDK. DPDK will adopt C11 atomic operations semantics and provide wrappers
us extending existing enum/define.
One solution can be using a fixed size array instead of ``.*MAX.*`` value.
-* pci: The PCI resources map API (``pci_map_resource`` and
- ``pci_unmap_resource``) was not abstracting the Unix mmap flags (see the
- workaround for Windows support implemented in the commit
- 9d2b24593724 ("pci: keep API compatibility with mmap values")).
- This API will be removed from the public API in 20.11 and moved to the PCI
- bus driver along with the PCI resources lists and associated structures
- (``pci_map``, ``pci_msix_table``, ``mapped_pci_resource`` and
- ``mapped_pci_res_list``).
- With this removal, there won't be a need for the mentioned workaround which
- will be reverted.
-
-* pci: The ``rte_kernel_driver`` enum defined in rte_dev.h will be made private
- to the PCI subsystem as it is used only by the PCI bus driver and PCI
- drivers.
- The associated field ``kdrv`` in the ethdev ``rte_eth_dev_data`` structure
- will be removed as it gave no useful abstracted information to the
- applications and had no user (neither internal nor external).
-
* mbuf: Some fields will be converted to dynamic API in DPDK 20.11
in order to reserve more space for the dynamic fields, as explained in
`this presentation <https://www.youtube.com/watch?v=Ttl6MlhmzWY>`_.
avoiding impact on vectorized implementation of the driver datapaths,
while evaluating performance gains of a better use of the first cache line.
- The deprecated unioned field ``buf_physaddr`` will be removed in DPDK 20.11.
-
-* ethdev: Split the ``struct eth_dev_ops`` struct to hide it as much as possible
- will be done in 20.11.
- Currently the ``struct eth_dev_ops`` struct is accessible by the application
- because some inline functions, like ``rte_eth_tx_descriptor_status()``,
- access the struct directly.
- The struct will be separate in two, the ops used by inline functions will be
- moved next to Rx/Tx burst functions, rest of the ``struct eth_dev_ops`` struct
- will be moved to header file for drivers to hide it from applications.
* ethdev: the legacy filter API, including
``rte_eth_dev_filter_supported()``, ``rte_eth_dev_filter_ctrl()`` as well
specified lengths into the buffers allocated from the specified
memory pools. The backward compatibility to existing API is preserved.
-* ethdev: The ``struct rte_eth_rxq_info`` will be modified to include
- a new optional field, indicating the buffer size used in receiving packets
- for HW. This change is planned for 20.11. For more details:
- https://mails.dpdk.org/archives/dev/2020-July/176135.html.
-
* ethdev: ``rx_descriptor_done`` dev_ops and ``rte_eth_rx_descriptor_done``
- will be deprecated in 20.11 and will be removed in 21.11.
+ will be removed in 21.11.
Existing ``rte_eth_rx_descriptor_status`` and ``rte_eth_tx_descriptor_status``
APIs can be used as replacement.
following the IPv6 header, as proposed in RFC
https://mails.dpdk.org/archives/dev/2020-August/177257.html.
-* ethdev: Some internal APIs for driver usage are exported in the .map file.
- Now DPDK has ``__rte_internal`` marker so we can mark internal APIs and move
- them to the INTERNAL block in .map. Although these APIs are internal it will
- break the ABI checks, that is why change is planned for 20.11.
- The list of internal APIs are mainly ones listed in ``rte_ethdev_driver.h``.
-
-* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made
- ABI stable in the v19.11 release. The TM maintainer and other contributors have
- agreed to keep the TM APIs as experimental in expectation of additional spec
- improvements. Therefore, all APIs in ``rte_tm.h`` will be marked back as
- experimental in v20.11 DPDK release. For more details, please see `the thread
- <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
-
-* pmd_dpaa: The API ``rte_pmd_dpaa_set_tx_loopback`` will have extended
- ``port_id`` definition from ``uint8_t`` to ``uint16_t``.
-
* vhost: Vhost-user dequeue zero-copy support will be removed in 20.11.
The only known user is OVS where the feature is still experimental,
and has not received any update for 2.5 years.
git.droids-corp.org / dpdk.git / blobdiff