4 .. **Read this first.**
6 The text in the sections below explains how to update the release notes.
8 Use proper spelling, capitalization and punctuation in all sections.
10 Variable and config names should be quoted as fixed width text:
13 Build the docs and view the output file to ensure the changes are correct::
17 xdg-open build/doc/html/guides/rel_notes/release_18_02.html
23 .. This section should contain new features added in this release. Sample
26 * **Add a title in the past tense with a full stop.**
28 Add a short 1-2 sentence description in the past tense. The description
29 should be enough to allow someone scanning the release notes to
30 understand the new feature.
32 If the feature adds a lot of sub-features you can use a bullet list like
35 * Added feature foo to do something.
36 * Enhanced feature bar to do something else.
38 Refer to the previous release notes for examples.
40 This section is a comment. do not overwrite or remove it.
41 Also, make sure to start the actual text at the margin.
42 =========================================================
44 * **Added the ixgbe ethernet driver to support RSS with flow API.**
46 Rte_flow actually defined to include RSS, but till now, RSS is out of
47 rte_flow. This patch is to support igb and ixgbe NIC with existing RSS
48 configuration using rte_flow API.
50 * **Add MAC loopback support for i40e.**
52 Add MAC loopback support for i40e in order to support test task asked by
53 users. According to the device configuration, it will setup TX->RX loopback
56 * **Add the support of run time determination of number of queues per i40e VF**
58 The number of queue per VF is determined by its host PF. If the PCI address
59 of an i40e PF is aaaa:bb.cc, the number of queues per VF can be configured
60 with EAL parameter like -w aaaa:bb.cc,queue-num-per-vf=n. The value n can be
61 1, 2, 4, 8 or 16. If no such parameter is configured, the number of queues
62 per VF is 4 by default.
64 * **Added the i40e ethernet driver to support RSS with flow API.**
66 Rte_flow actually defined to include RSS, but till now, RSS is out of
67 rte_flow. This patch is to support i40e NIC with existing RSS
68 configuration using rte_flow API.It also enable queue region configuration
69 using flow API for i40e.
71 * **Added NVGRE and UDP tunnels support in Solarflare network PMD.**
73 Added support for NVGRE, VXLAN and GENEVE tunnels.
75 * Added support for UDP tunnel ports configuration.
76 * Added tunneled packets classification.
77 * Added inner checksum offload.
79 * **Added the igb ethernet driver to support RSS with flow API.**
81 Rte_flow actually defined to include RSS, but till now, RSS is out of
82 rte_flow. This patch is to support igb NIC with existing RSS configuration
85 * **Add AVF (Adaptive Virtual Function) net PMD.**
87 A new net PMD has been added, which supports IntelĀ® Ethernet Adaptive
88 Virtual Function (AVF) with features list below:
91 * SSE vectorized Rx/Tx burst
96 * Jumbo frame and MTU setting
99 * Rx/Tx descriptor status
100 * Link status update/event
102 * **Updated the AESNI-MB PMD.**
104 The AESNI-MB PMD has been updated with additional support for:
108 * **Updated the DPAA_SEC crypto driver to support rte_security.**
110 Updated the ``dpaa_sec`` crypto PMD to support ``rte_security`` lookaside
111 protocol offload for IPSec.
113 * **Added Wireless Base Band Device (bbdev) abstraction.**
115 The Wireless Baseband Device library is an acceleration abstraction
116 framework for 3gpp Layer 1 processing functions that provides a common
117 programming interface for seamless opeartion on integrated or discrete
118 hardware accelerators or using optimized software libraries for signal
120 The current release only supports 3GPP CRC, Turbo Coding and Rate
121 Matching operations, as specified in 3GPP TS 36.212.
123 See the :doc:`../prog_guide/bbdev` programmer's guide for more details.
125 * **Added New eventdev OPDL PMD**
127 The OPDL (Ordered Packet Distribution Library) eventdev is a specific
128 implementation of the eventdev API. It is particularly suited to packet
129 processing workloads that have high throughput and low latency requirements.
130 All packets follow the same path through the device. The order in which
131 packets follow is determinted by the order in which queues are set up.
132 Events are left on the ring until they are transmitted. As a result packets
133 do not go out of order.
135 With this change, application can use OPDL PMD by eventdev api.
137 * **Added New pipeline use case for dpdk-test-eventdev application**
139 The pipeline case can be used to simulate various stages in a real world
140 application from packet receive to transmit while maintaining the packet
141 ordering also measure the performance of the event device across the stages
144 The pipeline use case has been made generic to work will all the event
145 devices based on the capabilities.
147 * **Updated Eventdev Sample application to support event devices based on capability**
149 Updated Eventdev pipeline sample application to support various types of pipelines
150 based on the capabilities of the attached event and ethernet devices. Also,
151 renamed the application from SW PMD specific ``eventdev_pipeline_sw_pmd``
152 to PMD agnostic ``eventdev_pipeline``.
158 .. This section should contain API changes. Sample format:
160 * Add a short 1-2 sentence description of the API change. Use fixed width
161 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
164 This section is a comment. do not overwrite or remove it.
165 Also, make sure to start the actual text at the margin.
166 =========================================================
172 .. This section should contain ABI changes. Sample format:
174 * Add a short 1-2 sentence description of the ABI change that was announced
175 in the previous releases and made in this release. Use fixed width quotes
176 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
178 This section is a comment. do not overwrite or remove it.
179 Also, make sure to start the actual text at the margin.
180 =========================================================
186 .. This section should contain removed items in this release. Sample format:
188 * Add a short 1-2 sentence description of the removed item in the past
191 This section is a comment. do not overwrite or remove it.
192 Also, make sure to start the actual text at the margin.
193 =========================================================
199 .. This section should contain new known issues in this release. Sample format:
201 * **Add title in present tense with full stop.**
203 Add a short 1-2 sentence description of the known issue in the present
204 tense. Add information on any known workarounds.
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 =========================================================
211 Shared Library Versions
212 -----------------------
214 .. Update any library version updated in this release and prepend with a ``+``
218 + librte_cfgfile.so.2
221 This section is a comment. do not overwrite or remove it.
222 =========================================================
225 The libraries prepended with a plus sign were incremented in this version.
231 librte_bitratestats.so.2
233 librte_bus_fslmc.so.1
238 librte_cryptodev.so.4
239 librte_distributor.so.1
243 librte_flow_classify.so.1
251 librte_latencystats.so.1
264 librte_pmd_ixgbe.so.2
266 librte_pmd_softnic.so.1
267 librte_pmd_vhost.so.2
283 .. This section should contain a list of platforms that were tested with this
288 * <vendor> platform with <vendor> <type of devices> combinations
293 * Other relevant details...
295 This section is a comment. do not overwrite or remove it.
296 Also, make sure to start the actual text at the margin.
297 =========================================================