1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2020 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::
22 xdg-open build/doc/html/guides/rel_notes/release_20_08.html
28 .. This section should contain new features added in this release.
31 * **Add a title in the past tense with a full stop.**
33 Add a short 1-2 sentence description in the past tense.
34 The description should be enough to allow someone scanning
35 the release notes to understand the new feature.
37 If the feature adds a lot of sub-features you can use a bullet list
40 * Added feature foo to do something.
41 * Enhanced feature bar to do something else.
43 Refer to the previous release notes for examples.
45 Suggested order in release notes items:
46 * Core libs (EAL, mempool, ring, mbuf, buses)
47 * Device abstraction libs and PMDs
49 - cryptodev (lib, PMDs)
50 - eventdev (lib, PMDs)
53 * Apps, Examples, Tools (if significant)
55 This section is a comment. Do not overwrite or remove it.
56 Also, make sure to start the actual text at the margin.
57 =========================================================
59 * **Updated PCAP driver.**
61 Updated PCAP driver with new features and improvements, including:
63 * Support software Tx nanosecond timestamps precision.
65 * **Updated Mellanox mlx5 driver.**
67 Updated Mellanox mlx5 driver with new features and improvements, including:
69 * Added new PMD devarg ``reclaim_mem_mode``.
71 * **Added support for BPF_ABS/BPF_IND load instructions.**
73 Added support for two BPF non-generic instructions:
74 ``(BPF_ABS | <size> | BPF_LD)`` and ``(BPF_IND | <size> | BPF_LD)``
75 which are used to access packet data in a safe manner. Currently JIT support
76 for these instructions is implemented for x86 only.
78 * **Added flow performance test application.**
80 Added new application to test ``rte_flow`` performance, including:
82 * Measure ``rte_flow`` insertion rate.
88 .. This section should contain removed items in this release. Sample format:
90 * Add a short 1-2 sentence description of the removed item
93 This section is a comment. Do not overwrite or remove it.
94 Also, make sure to start the actual text at the margin.
95 =========================================================
97 * Removed ``RTE_KDRV_NONE`` based PCI device driver probing.
103 .. This section should contain API changes. Sample format:
105 * sample: Add a short 1-2 sentence description of the API change
106 which was announced in the previous releases and made in this release.
107 Start with a scope label like "ethdev:".
108 Use fixed width quotes for ``function_names`` or ``struct_names``.
111 This section is a comment. Do not overwrite or remove it.
112 Also, make sure to start the actual text at the margin.
113 =========================================================
115 * ``rte_page_sizes`` enumeration is replaced with ``RTE_PGSIZE_xxx`` defines.
121 .. This section should contain ABI changes. Sample format:
123 * sample: Add a short 1-2 sentence description of the ABI change
124 which was announced in the previous releases and made in this release.
125 Start with a scope label like "ethdev:".
126 Use fixed width quotes for ``function_names`` or ``struct_names``.
129 This section is a comment. Do not overwrite or remove it.
130 Also, make sure to start the actual text at the margin.
131 =========================================================
133 * No ABI change that would break compatibility with 19.11.
139 .. This section should contain new known issues in this release. Sample format:
141 * **Add title in present tense with full stop.**
143 Add a short 1-2 sentence description of the known issue
144 in the present tense. Add information on any known workarounds.
146 This section is a comment. Do not overwrite or remove it.
147 Also, make sure to start the actual text at the margin.
148 =========================================================
154 .. This section should contain a list of platforms that were tested
159 * <vendor> platform with <vendor> <type of devices> combinations
164 * Other relevant details...
166 This section is a comment. Do not overwrite or remove it.
167 Also, make sure to start the actual text at the margin.
168 =========================================================