1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2022 The DPDK contributors
4 .. include:: <isonum.txt>
9 .. **Read this first.**
11 The text in the sections below explains how to update the release notes.
13 Use proper spelling, capitalization and punctuation in all sections.
15 Variable and config names should be quoted as fixed width text:
18 Build the docs and view the output file to ensure the changes are correct::
21 xdg-open build/doc/guides/html/rel_notes/release_22_07.html
27 .. This section should contain new features added in this release.
30 * **Add a title in the past tense with a full stop.**
32 Add a short 1-2 sentence description in the past tense.
33 The description should be enough to allow someone scanning
34 the release notes to understand the new feature.
36 If the feature adds a lot of sub-features you can use a bullet list
39 * Added feature foo to do something.
40 * Enhanced feature bar to do something else.
42 Refer to the previous release notes for examples.
44 Suggested order in release notes items:
45 * Core libs (EAL, mempool, ring, mbuf, buses)
46 * Device abstraction libs and PMDs (ordered alphabetically by vendor name)
48 - cryptodev (lib, PMDs)
49 - eventdev (lib, PMDs)
52 * Apps, Examples, Tools (if significant)
54 This section is a comment. Do not overwrite or remove it.
55 Also, make sure to start the actual text at the margin.
56 =======================================================
58 * **Added protocol based input color selection for meter.**
60 Added new functions ``rte_mtr_color_in_protocol_set()``,
61 ``rte_mtr_color_in_protocol_get()``,
62 ``rte_mtr_color_in_protocol_priority_get()``,
63 ``rte_mtr_meter_vlan_table_update()``
64 and updated ``struct rte_mtr_params`` and ``struct rte_mtr_capabilities`` to
65 support protocol based input color selection for meter.
67 * **Added vhost API to get the number of in-flight packets.**
69 Added an API which can get the number of in-flight packets in
70 vhost async data path without using lock.
72 * **Updated Intel iavf driver.**
74 * Added Tx QoS queue rate limitation support.
75 * Added quanta size configuration support.
76 * Added ``DEV_RX_OFFLOAD_TIMESTAMP`` support.
78 * **Updated Intel ice driver.**
80 * Added support for RSS RETA configure in DCF mode.
81 * Added support for RSS HASH configure in DCF mode.
82 * Added support for MTU configure in DCF mode.
83 * Added support for promisc configuration in DCF mode.
84 * Added support for MAC configuration in DCF mode.
85 * Added support for VLAN filter and offload configuration in DCF mode.
87 * **Updated Mellanox mlx5 driver.**
89 * Added support for promiscuous mode on Windows.
90 * Added support for MTU on Windows.
91 * Added matching and RSS on IPsec ESP.
93 * **Added Elliptic Curve Diffie-Hellman (ECDH) algorithm in cryptodev.**
95 Added support for Elliptic Curve Diffie Hellman (ECDH) asymmetric
96 algorithm in cryptodev.
98 * **Updated Marvell cnxk crypto driver.**
100 * Added AH mode support in lookaside protocol (IPsec) for CN9K & CN10K.
101 * Added AES-GMAC support in lookaside protocol (IPsec) for CN9K & CN10K.
103 * **Updated Intel QuickAssist Technology (QAT) crypto PMD.**
105 * Added support for secp384r1 elliptic curve.
107 * **Added eventdev API to quiesce an event port.**
109 Added the function ``rte_event_port_quiesce()``
110 to quiesce any lcore-specific resources consumed by the event port,
111 when the lcore is no more associated with an event port.
113 * **Added support for setting queue attributes at runtime in eventdev.**
115 Added new API ``rte_event_queue_attr_set()``, to set event queue attributes
118 * **Added new queues attributes weight and affinity in eventdev.**
120 Defined new event queue attributes weight and affinity as below:
122 * ``RTE_EVENT_QUEUE_ATTR_WEIGHT``
123 * ``RTE_EVENT_QUEUE_ATTR_AFFINITY``
125 * **Added scalar version of the LPM library.**
127 Added scalar implementation of ``rte_lpm_lookupx4``.
128 This is a fall-back implementation for platforms that
129 don't support vector operations.
135 .. This section should contain removed items in this release. Sample format:
137 * Add a short 1-2 sentence description of the removed item
140 This section is a comment. Do not overwrite or remove it.
141 Also, make sure to start the actual text at the margin.
142 =======================================================
148 .. This section should contain API changes. Sample format:
150 * sample: Add a short 1-2 sentence description of the API change
151 which was announced in the previous releases and made in this release.
152 Start with a scope label like "ethdev:".
153 Use fixed width quotes for ``function_names`` or ``struct_names``.
156 This section is a comment. Do not overwrite or remove it.
157 Also, make sure to start the actual text at the margin.
158 =======================================================
160 * The DPDK header file ``rte_altivec.h``,
161 which is a wrapper for the PPC header file ``altivec.h``,
162 undefines the AltiVec keyword ``vector``.
163 The alternative keyword ``__vector`` should be used instead.
165 * Experimental structures ``struct rte_mtr_params``
166 and ``struct rte_mtr_capabilities`` updated to support
167 protocol based input color for meter.
173 .. This section should contain ABI changes. Sample format:
175 * sample: Add a short 1-2 sentence description of the ABI change
176 which was announced in the previous releases and made in this release.
177 Start with a scope label like "ethdev:".
178 Use fixed width quotes for ``function_names`` or ``struct_names``.
181 This section is a comment. Do not overwrite or remove it.
182 Also, make sure to start the actual text at the margin.
183 =======================================================
185 * No ABI change that would break compatibility with 21.11.
191 .. This section should contain new known issues in this release. Sample format:
193 * **Add title in present tense with full stop.**
195 Add a short 1-2 sentence description of the known issue
196 in the present tense. Add information on any known workarounds.
198 This section is a comment. Do not overwrite or remove it.
199 Also, make sure to start the actual text at the margin.
200 =======================================================
206 .. This section should contain a list of platforms that were tested
211 * <vendor> platform with <vendor> <type of devices> combinations
216 * Other relevant details...
218 This section is a comment. Do not overwrite or remove it.
219 Also, make sure to start the actual text at the margin.
220 =======================================================