2022-07-09 08:43:09 +00:00
|
|
|
.. SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
Copyright 2022 The DPDK contributors
|
|
|
|
|
|
|
|
.. include:: <isonum.txt>
|
|
|
|
|
|
|
|
DPDK Release 22.11
|
|
|
|
==================
|
|
|
|
|
|
|
|
.. **Read this first.**
|
|
|
|
|
|
|
|
The text in the sections below explains how to update the release notes.
|
|
|
|
|
|
|
|
Use proper spelling, capitalization and punctuation in all sections.
|
|
|
|
|
|
|
|
Variable and config names should be quoted as fixed width text:
|
|
|
|
``LIKE_THIS``.
|
|
|
|
|
|
|
|
Build the docs and view the output file to ensure the changes are correct::
|
|
|
|
|
|
|
|
ninja -C build doc
|
|
|
|
xdg-open build/doc/guides/html/rel_notes/release_22_11.html
|
|
|
|
|
|
|
|
|
|
|
|
New Features
|
|
|
|
------------
|
|
|
|
|
|
|
|
.. This section should contain new features added in this release.
|
|
|
|
Sample format:
|
|
|
|
|
|
|
|
* **Add a title in the past tense with a full stop.**
|
|
|
|
|
|
|
|
Add a short 1-2 sentence description in the past tense.
|
|
|
|
The description should be enough to allow someone scanning
|
|
|
|
the release notes to understand the new feature.
|
|
|
|
|
|
|
|
If the feature adds a lot of sub-features you can use a bullet list
|
|
|
|
like this:
|
|
|
|
|
|
|
|
* Added feature foo to do something.
|
|
|
|
* Enhanced feature bar to do something else.
|
|
|
|
|
|
|
|
Refer to the previous release notes for examples.
|
|
|
|
|
|
|
|
Suggested order in release notes items:
|
|
|
|
* Core libs (EAL, mempool, ring, mbuf, buses)
|
|
|
|
* Device abstraction libs and PMDs (ordered alphabetically by vendor name)
|
|
|
|
- ethdev (lib, PMDs)
|
|
|
|
- cryptodev (lib, PMDs)
|
|
|
|
- eventdev (lib, PMDs)
|
|
|
|
- etc
|
|
|
|
* Other libs
|
|
|
|
* Apps, Examples, Tools (if significant)
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|
|
|
|
|
|
|
|
|
|
|
|
Removed Items
|
|
|
|
-------------
|
|
|
|
|
|
|
|
.. This section should contain removed items in this release. Sample format:
|
|
|
|
|
|
|
|
* Add a short 1-2 sentence description of the removed item
|
|
|
|
in the past tense.
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|
|
|
|
|
|
|
|
|
|
|
|
API Changes
|
|
|
|
-----------
|
|
|
|
|
|
|
|
.. This section should contain API changes. Sample format:
|
|
|
|
|
|
|
|
* sample: Add a short 1-2 sentence description of the API change
|
|
|
|
which was announced in the previous releases and made in this release.
|
|
|
|
Start with a scope label like "ethdev:".
|
|
|
|
Use fixed width quotes for ``function_names`` or ``struct_names``.
|
|
|
|
Use the past tense.
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|
|
|
|
|
2022-08-23 14:16:43 +00:00
|
|
|
* eal: RTE_FUNC_PTR_OR_* macros have been marked deprecated and will be removed
|
|
|
|
in the future. Applications can use ``devtools/cocci/func_or_ret.cocci``
|
|
|
|
to update their code.
|
|
|
|
|
2022-07-28 15:26:35 +00:00
|
|
|
* bus: Registering a bus has been marked as an internal API.
|
|
|
|
External users may still register their bus using the ``bus_driver.h``
|
|
|
|
driver header (see ``enable_driver_sdk`` meson option).
|
|
|
|
The ``rte_bus`` object is now opaque and must be manipulated through added
|
|
|
|
accessors.
|
|
|
|
|
2022-07-28 15:26:31 +00:00
|
|
|
* drivers: Registering a driver on the ``auxiliary``, ``ifpga``, ``pci``,
|
2022-07-28 15:26:32 +00:00
|
|
|
``vdev``, ``vmbus`` buses has been marked as an internal API.
|
2022-07-28 15:26:25 +00:00
|
|
|
External users may still register their driver using the associated driver
|
|
|
|
headers (see ``enable_driver_sdk`` meson option).
|
2022-07-28 15:26:40 +00:00
|
|
|
The ``rte_driver`` and ``rte_device`` objects are now opaque and must be
|
|
|
|
manipulated through added accessors.
|
2022-07-28 15:26:25 +00:00
|
|
|
|
2022-08-04 19:05:53 +00:00
|
|
|
* ethdev: Removed deprecated macros. Applications can use ``devtools/cocci/namespace_ethdev.cocci``
|
|
|
|
to update their code.
|
|
|
|
|
|
|
|
* Removed deprecated ``ETH_LINK_SPEED_*``, ``ETH_SPEED_NUM_*`` and ``ETH_LINK_*``
|
|
|
|
(duplex-related) defines. Use corresponding defines with ``RTE_`` prefix
|
|
|
|
instead.
|
|
|
|
|
2022-08-04 19:05:54 +00:00
|
|
|
* Removed deprecated ``ETH_MQ_RX_*`` and ``ETH_MQ_TX_*`` defines.
|
|
|
|
Use corresponding defines with ``RTE_`` prefix instead.
|
|
|
|
|
2022-08-04 19:05:55 +00:00
|
|
|
* Removed deprecated ``ETH_RSS_*`` defines for hash function and
|
|
|
|
RETA size specification. Use corresponding defines with ``RTE_`` prefix
|
|
|
|
instead.
|
|
|
|
|
2022-08-04 19:05:56 +00:00
|
|
|
* Removed deprecated ``DEV_RX_OFFLOAD_*`` and ``DEV_TX_OFFLOAD_``
|
|
|
|
defines. Use corresponding defines with ``RTE_ETH_RX_OFFLOAD_`` and
|
|
|
|
``RTE_ETH_TX_OFFLOAD_`` prefix instead.
|
|
|
|
|
2022-08-04 19:05:57 +00:00
|
|
|
* Removed deprecated ``ETH_DCB_*``, ``ETH_VMDQ_``, ``ETH_*_TCS``,
|
|
|
|
``ETH_*_POOLS`` and ``ETH_MAX_VMDQ_POOL`` defines. Use corresponding
|
|
|
|
defines with ``RTE_`` prefix instead.
|
|
|
|
|
2022-07-28 15:26:17 +00:00
|
|
|
* raw/ifgpa: The function ``rte_pmd_ifpga_get_pci_bus`` has been removed.
|
|
|
|
|
2022-07-09 08:43:09 +00:00
|
|
|
|
|
|
|
ABI Changes
|
|
|
|
-----------
|
|
|
|
|
|
|
|
.. This section should contain ABI changes. Sample format:
|
|
|
|
|
|
|
|
* sample: Add a short 1-2 sentence description of the ABI change
|
|
|
|
which was announced in the previous releases and made in this release.
|
|
|
|
Start with a scope label like "ethdev:".
|
|
|
|
Use fixed width quotes for ``function_names`` or ``struct_names``.
|
|
|
|
Use the past tense.
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|
|
|
|
|
|
|
|
|
|
|
|
Known Issues
|
|
|
|
------------
|
|
|
|
|
|
|
|
.. This section should contain new known issues in this release. Sample format:
|
|
|
|
|
|
|
|
* **Add title in present tense with full stop.**
|
|
|
|
|
|
|
|
Add a short 1-2 sentence description of the known issue
|
|
|
|
in the present tense. Add information on any known workarounds.
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|
|
|
|
|
|
|
|
|
|
|
|
Tested Platforms
|
|
|
|
----------------
|
|
|
|
|
|
|
|
.. This section should contain a list of platforms that were tested
|
|
|
|
with this release.
|
|
|
|
|
|
|
|
The format is:
|
|
|
|
|
|
|
|
* <vendor> platform with <vendor> <type of devices> combinations
|
|
|
|
|
|
|
|
* List of CPU
|
|
|
|
* List of OS
|
|
|
|
* List of devices
|
|
|
|
* Other relevant details...
|
|
|
|
|
|
|
|
This section is a comment. Do not overwrite or remove it.
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
=======================================================
|