1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2019 The DPDK contributors
7 .. **Read this first.**
9 The text in the sections below explains how to update the release notes.
11 Use proper spelling, capitalization and punctuation in all sections.
13 Variable and config names should be quoted as fixed width text:
16 Build the docs and view the output file to ensure the changes are correct::
20 xdg-open build/doc/html/guides/rel_notes/release_19_05.html
26 .. This section should contain new features added in this release.
29 * **Add a title in the past tense with a full stop.**
31 Add a short 1-2 sentence description in the past tense.
32 The description should be enough to allow someone scanning
33 the release notes to understand the new feature.
35 If the feature adds a lot of sub-features you can use a bullet list
38 * Added feature foo to do something.
39 * Enhanced feature bar to do something else.
41 Refer to the previous release notes for examples.
43 Suggested order in release notes items:
44 * Core libs (EAL, mempool, ring, mbuf, buses)
45 * Device abstraction libs and PMDs
47 - cryptodev (lib, PMDs)
48 - eventdev (lib, PMDs)
51 * Apps, Examples, Tools (if significant)
53 This section is a comment. Do not overwrite or remove it.
54 Also, make sure to start the actual text at the margin.
55 =========================================================
57 * **Updated Solarflare network PMD.**
59 Updated the sfc_efx driver including the following changes:
61 * Added support for Rx descriptor status and related API in a secondary
63 * Added support for Tx descriptor status API in a secondary process.
64 * Added support for RSS RETA and hash configuration get API in a secondary
66 * Added support for Rx packet types list in a secondary process.
68 * **Updated Mellanox drivers.**
70 New features and improvements were done in mlx4 and mlx5 PMDs:
72 * Added firmware version reading.
74 * **Renamed avf to iavf.**
76 Renamed Intel Ethernet Adaptive Virtual Function driver ``avf`` to ``iavf``,
77 which includes the directory name, lib name, filenames, makefile, docs,
78 macros, functions, structs and any other strings in the code.
80 * **Updated the enic driver.**
82 * Fixed several flow (director) bugs related to MARK, SCTP, VLAN, VXLAN, and
83 inner packet matching.
84 * Added limited support for RAW.
85 * Added limited support for RSS.
86 * Added limited support for PASSTHRU.
88 * **Updated the ixgbe driver.**
92 * Added promiscuous mode support.
94 * **Updated the QuickAssist Technology PMD.**
96 Added support for AES-XTS with 128 and 256 bit AES keys.
98 * **Updated the IPsec library.**
100 The IPsec library has been updated with AES-CTR cipher algorithm
101 support. The related ipsec-secgw test scripts have been added.
103 * **Updated the testpmd application.**
105 Improved testpmd application performance on ARM platform. For ``macswap``
106 forwarding mode, NEON intrinsics were used to do swap to save CPU cycles.
112 .. This section should contain removed items in this release. Sample format:
114 * Add a short 1-2 sentence description of the removed item
117 This section is a comment. Do not overwrite or remove it.
118 Also, make sure to start the actual text at the margin.
119 =========================================================
125 .. This section should contain API changes. Sample format:
127 * sample: Add a short 1-2 sentence description of the API change
128 which was announced in the previous releases and made in this release.
129 Start with a scope label like "ethdev:".
130 Use fixed width quotes for ``function_names`` or ``struct_names``.
133 This section is a comment. Do not overwrite or remove it.
134 Also, make sure to start the actual text at the margin.
135 =========================================================
141 .. This section should contain ABI changes. Sample format:
143 * sample: Add a short 1-2 sentence description of the ABI change
144 which was announced in the previous releases and made in this release.
145 Start with a scope label like "ethdev:".
146 Use fixed width quotes for ``function_names`` or ``struct_names``.
149 This section is a comment. Do not overwrite or remove it.
150 Also, make sure to start the actual text at the margin.
151 =========================================================
153 * cryptodev: in 18.08 new structure ``rte_crypto_asym_op`` was introduced and
154 included into ``rte_crypto_op``. As ``rte_crypto_asym_op`` structure was
155 defined as cache-line aligned that caused unintended changes in
156 ``rte_crypto_op`` structure layout and alignment. Remove cache-line
157 alignment for ``rte_crypto_asym_op`` to restore expected ``rte_crypto_op``
158 layout and alignment.
161 Shared Library Versions
162 -----------------------
164 .. Update any library version updated in this release
165 and prepend with a ``+`` sign, like this:
171 This section is a comment. Do not overwrite or remove it.
172 =========================================================
174 The libraries prepended with a plus sign were incremented in this version.
180 librte_bitratestats.so.2
183 librte_bus_fslmc.so.2
184 librte_bus_ifpga.so.2
187 librte_bus_vmbus.so.2
190 librte_compressdev.so.1
191 + librte_cryptodev.so.7
192 librte_distributor.so.1
197 librte_flow_classify.so.1
205 librte_latencystats.so.1
219 librte_pmd_ixgbe.so.2
220 librte_pmd_dpaa2_qdma.so.1
222 librte_pmd_softnic.so.1
223 librte_pmd_vhost.so.2
239 .. This section should contain new known issues in this release. Sample format:
241 * **Add title in present tense with full stop.**
243 Add a short 1-2 sentence description of the known issue
244 in the present tense. Add information on any known workarounds.
246 This section is a comment. Do not overwrite or remove it.
247 Also, make sure to start the actual text at the margin.
248 =========================================================
250 * **No software AES-XTS implementation.**
252 There are currently no cryptodev software PMDs available which implement
253 support for the AES-XTS algorithm, so this feature can only be used
254 if compatible hardware and an associated PMD is available.
260 .. This section should contain a list of platforms that were tested
265 * <vendor> platform with <vendor> <type of devices> combinations
270 * Other relevant details...
272 This section is a comment. Do not overwrite or remove it.
273 Also, make sure to start the actual text at the margin.
274 =========================================================