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_17_11.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 * **Extended port_id range from uint8_t to uint16_t.**
46 Increased port_id range from 8 bits to 16 bits in order to support more than
47 256 ports in dpdk. All ethdev APIs which have port_id as parameter are changed
50 * **Added a new driver for Marvell Armada 7k/8k devices.**
52 Added the new mrvl net driver for Marvell Armada 7k/8k devices. See the
53 "Network Interface Controller Drivers" document for more details on this new
56 * **nfp: Added PF support.**
58 Previously Netronome's NFP PMD had just support for VFs. PF support is
59 just as a basic DPDK port and has no VF management yet.
61 PF support comes with firmware upload support which allows the PMD to
62 independently work from kernel netdev NFP drivers.
64 NFP 4000 devices are also now supported along with previous 6000 devices.
66 * **Updated bnxt PMD.**
68 Major enhancements include:
70 * Support for Flow API
71 * Support for Tx and Rx descriptor status functions
73 * **Added IOMMU support to libvhost-user**
75 Implemented device IOTLB in Vhost-user backend, and enabled Virtio's IOMMU
78 * **Added Membership library (rte_member).**
80 Added membership library. It provides an API for DPDK applications to insert a
81 new member, delete an existing member, or query the existence of a member in a
82 given set, or a group of sets. For the case of a group of sets the library
83 will return not only whether the element has been inserted before in one of
84 the sets but also which set it belongs to.
86 The Membership Library is an extension and generalization of a traditional
87 filter (for example Bloom Filter) structure that has multiple usages in a wide
88 variety of workloads and applications. In general, the Membership Library is a
89 data structure that provides a “set-summary” and responds to set-membership
90 queries whether a certain member belongs to a set(s).
92 See the :ref:`Membership Library <Member_Library>` documentation in
93 the Programmers Guide document, for more information.
95 * **Added the Generic Segmentation Offload Library.**
97 Added the Generic Segmentation Offload (GSO) library to enable
98 applications to split large packets (e.g. MTU is 64KB) into small
99 ones (e.g. MTU is 1500B). Supported packet types are:
102 * VxLAN packets, which must have an outer IPv4 header, and contain
103 an inner TCP/IPv4 packet.
104 * GRE packets, which must contain an outer IPv4 header, and inner
107 The GSO library doesn't check if the input packets have correct
108 checksums, and doesn't update checksums for output packets.
109 Additionally, the GSO library doesn't process IP fragmented packets.
115 .. This section should contain bug fixes added to the relevant
116 sections. Sample format:
118 * **code/section Fixed issue in the past tense with a full stop.**
120 Add a short 1-2 sentence description of the resolved issue in the past
123 The title should contain the code/lib section like a commit message.
125 Add the entries in alphabetic order in the relevant sections below.
127 This section is a comment. do not overwrite or remove it.
128 Also, make sure to start the actual text at the margin.
129 =========================================================
135 * **Service core fails to call service callback due to atomic lock**
137 In a specific configuration of multi-thread unsafe services and service
138 cores, a service core previously did not correctly release the atomic lock
139 on the service. This would result in the cores polling the service, but it
140 looked like another thread was executing the service callback. The logic for
141 atomic locking of the services has been fixed and refactored for readability.
162 .. This section should contain new known issues in this release. Sample format:
164 * **Add title in present tense with full stop.**
166 Add a short 1-2 sentence description of the known issue in the present
167 tense. Add information on any known workarounds.
169 This section is a comment. do not overwrite or remove it.
170 Also, make sure to start the actual text at the margin.
171 =========================================================
177 .. This section should contain API changes. Sample format:
179 * Add a short 1-2 sentence description of the API change. Use fixed width
180 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
183 This section is a comment. do not overwrite or remove it.
184 Also, make sure to start the actual text at the margin.
185 =========================================================
187 * **Ethdev device name length increased**
189 The size of internal device name is increased to 64 characters
190 to allow for storing longer bus specific name.
192 * **Service cores API updated for usability**
194 The service cores API has been changed, removing pointers from the API
195 where possible, instead using integer IDs to identify each service. This
196 simplifed application code, aids debugging, and provides better
197 encapsulation. A summary of the main changes made is as follows:
199 * Services identified by ID not by ``rte_service_spec`` pointer
200 * Reduced API surface by using ``set`` functions instead of enable/disable
201 * Reworked ``rte_service_register`` to provide the service ID to registrar
202 * Rework start and stop APIs into ``rte_service_runstate_set``
203 * Added API to set runstate of service implementation to indicate readyness
205 * **The following changes made in mempool library**
207 * Moved ``flags`` datatype from int to unsigned int for ``rte_mempool``.
208 * Removed ``__rte_unused int flag`` param from ``rte_mempool_generic_put``
209 and ``rte_mempool_generic_get`` API.
210 * Added ``flags`` param in ``rte_mempool_xmem_size`` and
211 ``rte_mempool_xmem_usage``.
213 * Xen dom0 in EAL was removed, as well as xenvirt PMD and vhost_xen.
215 * ``rte_mem_phy2mch`` was used in Xen dom0 to obtain the physical address;
216 remove this API as Xen dom0 support was removed.
222 .. This section should contain ABI changes. Sample format:
224 * Add a short 1-2 sentence description of the ABI change that was announced
225 in the previous releases and made in this release. Use fixed width quotes
226 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
228 This section is a comment. do not overwrite or remove it.
229 Also, make sure to start the actual text at the margin.
230 =========================================================
232 * **Extended port_id range.**
234 The size of the field ``port_id`` in the ``rte_eth_dev_data`` structure
235 changed, as described in the `New Features` section.
237 Shared Library Versions
238 -----------------------
240 .. Update any library version updated in this release and prepend with a ``+``
244 + librte_cfgfile.so.2
247 This section is a comment. do not overwrite or remove it.
248 =========================================================
251 The libraries prepended with a plus sign were incremented in this version.
256 librte_bitratestats.so.2
259 librte_cryptodev.so.3
260 librte_distributor.so.1
271 librte_latencystats.so.1
283 librte_pmd_ixgbe.so.2
285 librte_pmd_vhost.so.2
299 .. This section should contain a list of platforms that were tested with this
304 * <vendor> platform with <vendor> <type of devices> combinations
309 * Other relevant details...
311 This section is a comment. do not overwrite or remove it.
312 Also, make sure to start the actual text at the margin.
313 =========================================================