1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright 2022 The DPDK contributors 3 4.. include:: <isonum.txt> 5 6DPDK Release 23.03 7================== 8 9.. **Read this first.** 10 11 The text in the sections below explains how to update the release notes. 12 13 Use proper spelling, capitalization and punctuation in all sections. 14 15 Variable and config names should be quoted as fixed width text: 16 ``LIKE_THIS``. 17 18 Build the docs and view the output file to ensure the changes are correct:: 19 20 ninja -C build doc 21 xdg-open build/doc/guides/html/rel_notes/release_23_03.html 22 23 24New Features 25------------ 26 27.. This section should contain new features added in this release. 28 Sample format: 29 30 * **Add a title in the past tense with a full stop.** 31 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. 35 36 If the feature adds a lot of sub-features you can use a bullet list 37 like this: 38 39 * Added feature foo to do something. 40 * Enhanced feature bar to do something else. 41 42 Refer to the previous release notes for examples. 43 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) 47 - ethdev (lib, PMDs) 48 - cryptodev (lib, PMDs) 49 - eventdev (lib, PMDs) 50 - etc 51 * Other libs 52 * Apps, Examples, Tools (if significant) 53 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 ======================================================= 57 58* **Introduced lock annotations.** 59 60 Added lock annotations attributes so that clang can statically analyze lock 61 correctness. 62 63* **Added support for reporting lcore usage in applications.** 64 65 * The ``/eal/lcore/list``, ``/eal/lcore/usage`` and ``/eal/lcore/info`` 66 telemetry endpoints have been added to provide information similar to 67 ``rte_lcore_dump()``. 68 * Applications can register a callback at startup via 69 ``rte_lcore_register_usage_cb()`` to provide lcore usage information. 70 71* **Added flow matching of IPv6 routing extension.** 72 73 Added ``RTE_FLOW_ITEM_TYPE_IPV6_ROUTING_EXT`` 74 to match IPv6 routing extension header fields. 75 76* **Updated AMD axgbe driver.** 77 78 * Added multi-process support. 79 80* **Updated Corigine nfp driver.** 81 82 * Added support for meter options. 83 * Added support for rte_flow meter action. 84 85* **Updated Wangxun ngbe driver.** 86 87 * Added chip overheat detection support. 88 89* **Updated Wangxun txgbe driver.** 90 91 * Added chip overheat detection support. 92 * Added SFP hot-plug identification support. 93 94* **Added new algorithms to cryptodev.** 95 96 Added SHAKE-128 and SHAKE-256 symmetric secure hash algorithm. 97 98* **Updated Marvell cnxk crypto driver.** 99 100 Added support for SHAKE hash algorithm in cn9k and cn10k. 101 102* **Updated Intel QuickAssist Technology (QAT) crypto driver.** 103 104 * Added support for SHA3 224/256/384/512 plain hash in QAT GEN 3. 105 * Added support for SHA3 256 plain hash in QAT GEN 2. 106 * Added support for asymmetric crypto in QAT GEN3. 107 108* **Updated the eventdev reconfigure logic for service based adapters.** 109 110 * eventdev reconfig logic is enhanced to increment the 111 ``rte_event_dev_config::nb_single_link_event_port_queues`` parameter 112 if event port config is of type ``RTE_EVENT_PORT_CFG_SINGLE_LINK``. 113 * With this change, the application no longer needs to account for the 114 ``rte_event_dev_config::nb_single_link_event_port_queues`` parameter 115 required for eth_rx, eth_tx, crypto and timer eventdev adapters. 116 117* **Added pcap trace support in graph library.** 118 119 * Added support to capture packets at each graph node with packet metadata and 120 node name. 121 122 123Removed Items 124------------- 125 126.. This section should contain removed items in this release. Sample format: 127 128 * Add a short 1-2 sentence description of the removed item 129 in the past tense. 130 131 This section is a comment. Do not overwrite or remove it. 132 Also, make sure to start the actual text at the margin. 133 ======================================================= 134 135 136API Changes 137----------- 138 139.. This section should contain API changes. Sample format: 140 141 * sample: Add a short 1-2 sentence description of the API change 142 which was announced in the previous releases and made in this release. 143 Start with a scope label like "ethdev:". 144 Use fixed width quotes for ``function_names`` or ``struct_names``. 145 Use the past tense. 146 147 This section is a comment. Do not overwrite or remove it. 148 Also, make sure to start the actual text at the margin. 149 ======================================================= 150 151* The experimental function ``rte_pcapng_copy`` was updated to support comment 152 section in enhanced packet block in the pcapng library. 153 154* The experimental structures ``struct rte_graph_param``, ``struct rte_graph`` 155 and ``struct graph`` were updated to support pcap trace in the graph library. 156 157 158ABI Changes 159----------- 160 161.. This section should contain ABI changes. Sample format: 162 163 * sample: Add a short 1-2 sentence description of the ABI change 164 which was announced in the previous releases and made in this release. 165 Start with a scope label like "ethdev:". 166 Use fixed width quotes for ``function_names`` or ``struct_names``. 167 Use the past tense. 168 169 This section is a comment. Do not overwrite or remove it. 170 Also, make sure to start the actual text at the margin. 171 ======================================================= 172 173* No ABI change that would break compatibility with 22.11. 174 175 176Known Issues 177------------ 178 179.. This section should contain new known issues in this release. Sample format: 180 181 * **Add title in present tense with full stop.** 182 183 Add a short 1-2 sentence description of the known issue 184 in the present tense. Add information on any known workarounds. 185 186 This section is a comment. Do not overwrite or remove it. 187 Also, make sure to start the actual text at the margin. 188 ======================================================= 189 190 191Tested Platforms 192---------------- 193 194.. This section should contain a list of platforms that were tested 195 with this release. 196 197 The format is: 198 199 * <vendor> platform with <vendor> <type of devices> combinations 200 201 * List of CPU 202 * List of OS 203 * List of devices 204 * Other relevant details... 205 206 This section is a comment. Do not overwrite or remove it. 207 Also, make sure to start the actual text at the margin. 208 ======================================================= 209