1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright 2024 The DPDK contributors 3 4.. include:: <isonum.txt> 5 6DPDK Release 25.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_25_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* **Added Staged-Ordered-Ring (SORING) API to the ring library.** 59 60 New API was added to the ring library to provide a SW abstraction 61 for ordered queues with multiple processing stages. 62 It is based on conventional DPDK rte_ring, re-uses many of its concepts, 63 and even substantial part of its code. 64 It can be viewed as an extension of rte_ring functionality. 65 66* **Updated af_packet net driver.** 67 68 * Added ability to option to configure receive packet fanout mode. 69 * Added statistics for failed buffer allocation and missed packets. 70 71* **Updated AMD axgbe driver.** 72 73 * Added support for the TCP Segmentation Offload (TSO). 74 75* **Updated Wangxun ngbe driver.** 76 77 * Added support for virtual function (VF). 78 79 80Removed Items 81------------- 82 83.. This section should contain removed items in this release. Sample format: 84 85 * Add a short 1-2 sentence description of the removed item 86 in the past tense. 87 88 This section is a comment. Do not overwrite or remove it. 89 Also, make sure to start the actual text at the margin. 90 ======================================================= 91 92 93API Changes 94----------- 95 96.. This section should contain API changes. Sample format: 97 98 * sample: Add a short 1-2 sentence description of the API change 99 which was announced in the previous releases and made in this release. 100 Start with a scope label like "ethdev:". 101 Use fixed width quotes for ``function_names`` or ``struct_names``. 102 Use the past tense. 103 104 This section is a comment. Do not overwrite or remove it. 105 Also, make sure to start the actual text at the margin. 106 ======================================================= 107 108* eal: The ``__rte_packed`` macro for packing data is replaced with 109 ``__rte_packed_begin`` / ``__rte_packed_end``. 110 111* build: The Intel networking drivers: 112 cpfl, e1000, fm10k, i40e, iavf, ice, idpf, igc, ipn3ke and ixgbe, 113 have been moved from ``drivers/net`` to a new ``drivers/net/intel`` directory. 114 The resulting build output, including the driver filenames, is the same, 115 but to enable/disable these drivers via Meson option requires use of the new paths. 116 For example, ``-Denable_drivers=/net/i40e`` becomes ``-Denable_drivers=/net/intel/i40e``. 117 118 119ABI Changes 120----------- 121 122.. This section should contain ABI changes. Sample format: 123 124 * sample: Add a short 1-2 sentence description of the ABI change 125 which was announced in the previous releases and made in this release. 126 Start with a scope label like "ethdev:". 127 Use fixed width quotes for ``function_names`` or ``struct_names``. 128 Use the past tense. 129 130 This section is a comment. Do not overwrite or remove it. 131 Also, make sure to start the actual text at the margin. 132 ======================================================= 133 134* No ABI change that would break compatibility with 24.11. 135 136 137Known Issues 138------------ 139 140.. This section should contain new known issues in this release. Sample format: 141 142 * **Add title in present tense with full stop.** 143 144 Add a short 1-2 sentence description of the known issue 145 in the present tense. Add information on any known workarounds. 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 152Tested Platforms 153---------------- 154 155.. This section should contain a list of platforms that were tested 156 with this release. 157 158 The format is: 159 160 * <vendor> platform with <vendor> <type of devices> combinations 161 162 * List of CPU 163 * List of OS 164 * List of devices 165 * Other relevant details... 166 167 This section is a comment. Do not overwrite or remove it. 168 Also, make sure to start the actual text at the margin. 169 ======================================================= 170