4 .. **Read this first.**
6 The text 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: ``LIKE_THIS``.
12 Build the docs and view the output file to ensure the changes are correct::
16 firefox build/doc/html/guides/rel_notes/release_17_02.html
22 .. This section should contain new features added in this release. Sample format:
24 * **Add a title in the past tense with a full stop.**
26 Add a short 1-2 sentence description in the past tense. The description
27 should be enough to allow someone scanning the release notes to understand
30 If the feature adds a lot of sub-features you can use a bullet list like this.
32 * Added feature foo to do something.
33 * Enhanced feature bar to do something else.
35 Refer to the previous release notes for examples.
37 This section is a comment. do not overwrite or remove it.
38 Also, make sure to start the actual text at the margin.
39 =========================================================
41 * **Added generic EAL API for I/O device memory read/write operations.**
43 This API introduces 8-bit, 16-bit, 32bit, 64bit I/O device
44 memory read/write operations along with the relaxed versions.
46 The weakly-ordered machine like ARM needs additional I/O barrier for
47 device memory read/write access over PCI bus.
48 By introducing the EAL abstraction for I/O device memory read/write access,
49 The drivers can access I/O device memory in architecture-agnostic manner.
50 The relaxed version does not have additional I/O memory barrier, useful in
51 accessing the device registers of integrated controllers which
52 implicitly strongly ordered with respect to memory access.
54 * **Added generic flow API (rte_flow).**
56 This API provides a generic means to configure hardware to match specific
57 ingress or egress traffic, alter its fate and query related counters
58 according to any number of user-defined rules.
60 It is slightly higher-level than the legacy filtering framework which it
61 encompasses and supersedes (including all functions and filter types) in
62 order to expose a single interface with an unambiguous behavior that is
63 common to all poll-mode drivers (PMDs).
65 See the :ref:`Generic flow API <Generic_flow_API>` documentation for more
68 * **Added firmware version get API.**
70 Added a new function ``rte_eth_dev_fw_version_get()`` to fetch firmware
71 version by a given device.
73 * **Added APIs for MACsec offload support to the ixgbe PMD.**
75 Six new APIs have been added to the ixgbe PMD for MACsec offload support.
76 The declarations for the APIs can be found in ``rte_pmd_ixgbe.h``.
78 * **Added I219 NICs support.**
80 Added support for I219 Intel 1GbE NICs.
82 * **Added VF Daemon (VFD) on i40e. - EXPERIMENTAL**
84 This's an EXPERIMENTAL feature to enhance the capability of DPDK PF as many
85 VF management features are not supported by kernel PF driver.
86 Some new private APIs are implemented in PMD without abstrction layer.
87 They can be used directly by some users who have the need.
89 The new APIs to control VFs directly from PF include,
90 1) set VF MAC anti-spoofing
91 2) set VF VLAN anti-spoofing
93 4) set VF unicast promiscuous mode
94 5) set VF multicast promiscuous mode
98 9) set VF VLAN stripping
100 12) set VF broadcast mode
102 14) set VF VLAN filter
103 VFD also includes VF to PF mailbox message management by APP.
104 When PF receives mailbox messages from VF, PF should call the callback
105 provided by APP to know if they're permitted to be processed.
107 As an EXPERIMENTAL feature, please aware it can be changed or even
108 removed without prior notice.
110 * **Updated the i40e base driver.**
112 updated the i40e base driver, including the following changes:
114 * replace existing legacy memcpy() calls with i40e_memcpy() calls.
115 * use BIT() macro instead of bit fields
116 * add clear all WoL filters implementation
117 * add broadcast promiscuous control per VLAN
118 * remove unused X722_SUPPORT and I40E_NDIS_SUPPORT MARCOs
120 * **Added Solarflare libefx-based network PMD.**
122 A new network PMD which supports Solarflare SFN7xxx and SFN8xxx family
123 of 10/40 Gbps adapters has been added.
125 * **Added support for Mellanox ConnectX-5 adapters (mlx5).**
127 Support for Mellanox ConnectX-5 family of 10/25/40/50/100 Gbps adapters
128 has been added to the existing mlx5 PMD.
130 * **virtio-user with vhost-kernel as another exceptional path.**
132 Previously, we upstreamed a virtual device, virtio-user with vhost-user
133 as the backend, as a way for IPC (Inter-Process Communication) and user
134 space container networking.
136 Virtio-user with vhost-kernel as the backend is a solution for exceptional
137 path, such as KNI, which exchanges packets with kernel networking stack.
138 This solution is very promising in:
140 * maintenance: vhost and vhost-net (kernel) is upstreamed and extensively
142 * features: vhost-net is born to be a networking solution, which has
143 lots of networking related features, like multi-queue, TSO, multi-seg
145 * performance: similar to KNI, this solution would use one or more
146 kthreads to send/receive packets from user space DPDK applications,
147 which has little impact on user space polling thread (except that
148 it might enter into kernel space to wake up those kthreads if
151 * **Added virtio Rx interrupt suppprt.**
153 This feature enables Rx interrupt mode for virtio pci net devices as
154 binded to VFIO (noiommu mode) and drived by virtio PMD.
156 With this feature, virtio PMD can switch between polling mode and
157 interrupt mode, to achieve best performance, and at the same time save
158 power. It can work on both legacy and modern virtio devices. At this mode,
159 each rxq is mapped with an exluded MSIx interrupt.
161 See the :ref:`Virtio Interrupt Mode <virtio_interrupt_mode>` documentation
162 for more information.
164 * **Added ARMv8 crypto PMD.**
166 A new crypto PMD has been added, which provides combined mode cryptografic
167 operations optimized for ARMv8 processors. The driver can be used to enhance
168 performance in processing chained operations such as cipher + HMAC.
170 * **Updated the QAT PMD.**
172 The QAT PMD was updated with additional support for:
175 * Scatter-gather list (SGL) support.
177 * **Updated the AESNI MB PMD.**
179 * The Intel(R) Multi Buffer Crypto for IPsec library used in
180 AESNI MB PMD has been moved to a new repository, in GitHub.
181 * Support for single operations (cipher only and authentication only).
183 * **Updated the AES-NI GCM PMD.**
185 The AES-NI GCM PMD was migrated from MB library to ISA-L library.
186 The migration entailed the following additional support for:
189 * 256-bit cipher key.
191 * Out-of place processing
192 * Scatter-gatter support for chained mbufs (only out-of place and destination
193 mbuf must be contiguous)
195 * **Added crypto performance test application.**
197 A new performance test application allows measuring performance parameters
198 of PMDs available in crypto tree.
200 * **Added Elastic Flow Distributor library (rte_efd).**
202 This new library uses perfect hashing to determine a target/value for a
203 given incoming flow key.
205 It does not store the key itself for lookup operations, and therefore,
206 lookup performance is not dependent on the key size. Also, the target/value
207 can be any arbitrary value (8 bits by default). Finally, the storage requirement
208 is much smaller than a hash-based flow table and therefore, it can better fit for
209 CPU cache, being able to scale to millions of flow keys.
211 See the :ref:`Elastic Flow Distributor Library <Efd_Library>` documentation in
212 the Programmers Guide document, for more information.
218 .. This section should contain bug fixes added to the relevant sections. Sample format:
220 * **code/section Fixed issue in the past tense with a full stop.**
222 Add a short 1-2 sentence description of the resolved issue in the past tense.
223 The title should contain the code/lib section like a commit message.
224 Add the entries in alphabetic order in the relevant sections below.
226 This section is a comment. do not overwrite or remove it.
227 Also, make sure to start the actual text at the margin.
228 =========================================================
238 * **net/virtio: Fixed multiple process support.**
240 Fixed few regressions introduced in recent releases that break the virtio
241 multiple process support.
251 * **examples/ethtool: Fixed crash with non-PCI devices.**
253 Querying a non-PCI device was dereferencing non-existent PCI data
254 resulting in a segmentation fault.
264 .. This section should contain new known issues in this release. Sample format:
266 * **Add title in present tense with full stop.**
268 Add a short 1-2 sentence description of the known issue in the present
269 tense. Add information on any known workarounds.
271 This section is a comment. do not overwrite or remove it.
272 Also, make sure to start the actual text at the margin.
273 =========================================================
279 .. This section should contain API changes. Sample format:
281 * Add a short 1-2 sentence description of the API change. Use fixed width
282 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
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 =========================================================
288 * **Moved five APIs for VF management from the ethdev to the ixgbe PMD.**
290 The following five APIs for VF management from the PF have been removed from the ethdev,
291 renamed and added to the ixgbe PMD::
293 rte_eth_dev_set_vf_rate_limit
294 rte_eth_dev_set_vf_rx
295 rte_eth_dev_set_vf_rxmode
296 rte_eth_dev_set_vf_tx
297 rte_eth_dev_set_vf_vlan_filter
299 The API's have been renamed to the following::
301 rte_pmd_ixgbe_set_vf_rate_limit
302 rte_pmd_ixgbe_set_vf_rx
303 rte_pmd_ixgbe_set_vf_rxmode
304 rte_pmd_ixgbe_set_vf_tx
305 rte_pmd_ixgbe_set_vf_vlan_filter
307 The declarations for the API’s can be found in ``rte_pmd_ixgbe.h``.
312 .. This section should contain ABI changes. Sample format:
314 * Add a short 1-2 sentence description of the ABI change that was announced in
315 the previous releases and made in this release. Use fixed width quotes for
316 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
318 This section is a comment. do not overwrite or remove it.
319 Also, make sure to start the actual text at the margin.
320 =========================================================
324 Shared Library Versions
325 -----------------------
327 .. Update any library version updated in this release and prepend with a ``+``
331 + librte_cfgfile.so.2
334 This section is a comment. do not overwrite or remove it.
335 =========================================================
338 The libraries prepended with a plus sign were incremented in this version.
345 librte_cryptodev.so.2
346 librte_distributor.so.1
376 .. This section should contain a list of platforms that were tested with this release.
385 This section is a comment. do not overwrite or remove it.
386 Also, make sure to start the actual text at the margin.
387 =========================================================
393 .. This section should contain a list of NICs that were tested with this release.
402 This section is a comment. do not overwrite or remove it.
403 Also, make sure to start the actual text at the margin.
404 =========================================================
410 .. This section should contain a list of OSes that were tested with this release.
411 The format is as follows, in alphabetical order:
417 * Red Hat Enterprise Linux 7.2
418 * SUSE Enterprise Linux 12
423 This section is a comment. do not overwrite or remove it.
424 Also, make sure to start the actual text at the margin.
425 =========================================================