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 * **Added Wireless Base Band Device (bbdev) abstraction.**
104 The Wireless Baseband Device library is an acceleration abstraction
105 framework for 3gpp Layer 1 processing functions that provides a common
106 programming interface for seamless opeartion on integrated or discrete
107 hardware accelerators or using optimized software libraries for signal
109 The current release only supports 3GPP CRC, Turbo Coding and Rate
110 Matching operations, as specified in 3GPP TS 36.212.
112 See the :doc:`../prog_guide/bbdev` programmer's guide for more details.
114 * **Added New eventdev OPDL PMD**
116 The OPDL (Ordered Packet Distribution Library) eventdev is a specific
117 implementation of the eventdev API. It is particularly suited to packet
118 processing workloads that have high throughput and low latency requirements.
119 All packets follow the same path through the device. The order in which
120 packets follow is determinted by the order in which queues are set up.
121 Events are left on the ring until they are transmitted. As a result packets
122 do not go out of order.
124 With this change, application can use OPDL PMD by eventdev api.
126 * **Added New pipeline use case for dpdk-test-eventdev application**
128 The pipeline case can be used to simulate various stages in a real world
129 application from packet receive to transmit while maintaining the packet
130 ordering also measure the performance of the event device across the stages
133 The pipeline use case has been made generic to work will all the event
134 devices based on the capabilities.
136 * **Updated Eventdev Sample application to support event devices based on capability**
138 Updated Eventdev pipeline sample application to support various types of pipelines
139 based on the capabilities of the attached event and ethernet devices. Also,
140 renamed the application from SW PMD specific ``eventdev_pipeline_sw_pmd``
141 to PMD agnostic ``eventdev_pipeline``.
147 .. This section should contain API changes. Sample format:
149 * Add a short 1-2 sentence description of the API change. Use fixed width
150 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
153 This section is a comment. do not overwrite or remove it.
154 Also, make sure to start the actual text at the margin.
155 =========================================================
161 .. This section should contain ABI changes. Sample format:
163 * Add a short 1-2 sentence description of the ABI change that was announced
164 in the previous releases and made in this release. Use fixed width quotes
165 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
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 =========================================================
175 .. This section should contain removed items in this release. Sample format:
177 * Add a short 1-2 sentence description of the removed item in the past
180 This section is a comment. do not overwrite or remove it.
181 Also, make sure to start the actual text at the margin.
182 =========================================================
188 .. This section should contain new known issues in this release. Sample format:
190 * **Add title in present tense with full stop.**
192 Add a short 1-2 sentence description of the known issue in the present
193 tense. Add information on any known workarounds.
195 This section is a comment. do not overwrite or remove it.
196 Also, make sure to start the actual text at the margin.
197 =========================================================
200 Shared Library Versions
201 -----------------------
203 .. Update any library version updated in this release and prepend with a ``+``
207 + librte_cfgfile.so.2
210 This section is a comment. do not overwrite or remove it.
211 =========================================================
214 The libraries prepended with a plus sign were incremented in this version.
220 librte_bitratestats.so.2
222 librte_bus_fslmc.so.1
227 librte_cryptodev.so.4
228 librte_distributor.so.1
232 librte_flow_classify.so.1
240 librte_latencystats.so.1
253 librte_pmd_ixgbe.so.2
255 librte_pmd_softnic.so.1
256 librte_pmd_vhost.so.2
272 .. This section should contain a list of platforms that were tested with this
277 * <vendor> platform with <vendor> <type of devices> combinations
282 * Other relevant details...
284 This section is a comment. do not overwrite or remove it.
285 Also, make sure to start the actual text at the margin.
286 =========================================================