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_05.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 bucket mempool driver.**
46 Added bucket mempool driver which provides a way to allocate contiguous
48 Number of objects in the block depends on how many objects fit in
49 RTE_DRIVER_MEMPOOL_BUCKET_SIZE_KB memory chunk which is build time option.
51 * **Added PMD-recommended Tx and Rx parameters**
53 Applications can now query drivers for device-tuned values of
54 ring sizes, burst sizes, and number of queues.
56 * **Added RSS hash and key update to CXGBE PMD.**
58 Support to update RSS hash and key has been added to CXGBE PMD.
60 * **Added CXGBE VF PMD.**
62 CXGBE VF Poll Mode Driver has been added to run DPDK over Chelsio
63 T5/T6 NIC VF instances.
65 * **Updated Solarflare network PMD.**
67 Updated the sfc_efx driver including the following changes:
69 * Added support for Solarflare XtremeScale X2xxx family adapters.
70 * Added support for NVGRE, VXLAN and GENEVE filters in flow API.
71 * Added support for DROP action in flow API.
73 * **Added Ethernet poll mode driver for AMD XGBE devices.**
75 Added the new ``axgbe`` ethernet poll mode driver for AMD XGBE devices.
76 See the :doc:`../nics/axgbe` nic driver guide for more details on this
79 * **Updated szedata2 PMD.**
81 Added support for new NFB-200G2QL card.
83 * **Added support for Broadcom NetXtreme-S (BCM58800) family of controllers (aka Stingray)**
85 The BCM58800 devices feature a NetXtreme E-Series advanced network controller, a high-performance
86 ARM CPU block, PCI Express (PCIe) Gen3 interfaces, key accelerators for compute offload and a high-
87 speed memory subsystem including L3 cache and DDR4 interfaces, all interconnected by a coherent
88 Network-on-chip (NOC) fabric.
90 The ARM CPU subsystem features eight ARMv8 Cortex-A72 CPUs at 3.0 GHz, arranged in a multi-cluster
93 * **Added support for virtio-user server mode.**
94 In a container environment if the vhost-user backend restarts, there's no way
95 for it to reconnect to virtio-user. To address this, support for server mode
96 is added. In this mode the socket file is created by virtio-user, which the
97 backend connects to. This means that if the backend restarts, it can reconnect
98 to virtio-user and continue communications.
100 * **Added crypto workload support to vhost library.**
102 New APIs are introduced in vhost library to enable virtio crypto support
103 including session creation/deletion handling and translating virtio-crypto
104 request into DPDK crypto operations. A sample application is also introduced.
106 * **Added virtio crypto PMD.**
108 Added a new poll mode driver for virtio crypto devices, which provides
109 AES-CBC ciphering and AES-CBC with HMAC-SHA1 algorithm-chaining. See the
110 :doc:`../cryptodevs/virtio` crypto driver guide for more details on
113 * **Added AMD CCP Crypto PMD.**
115 Added the new ``ccp`` crypto driver for AMD CCP devices. See the
116 :doc:`../cryptodevs/ccp` crypto driver guide for more details on
119 * **Updated AESNI MB PMD.**
121 The AESNI MB PMD has been updated with additional support for:
123 * AES-CMAC (128-bit key).
125 * **Added the Event Timer Adapter Library.**
127 The Event Timer Adapter Library extends the event-based model by introducing
128 APIs that allow applications to arm/cancel event timers that generate
129 timer expiry events. This new type of event is scheduled by an event device
130 along with existing types of events.
132 * **Added device event monitor framework.**
134 Added a general device event monitor framework at EAL, for device dynamic management.
135 Such as device hotplug awareness and actions adopted accordingly. The list of new APIs:
137 * ``rte_dev_event_monitor_start`` and ``rte_dev_event_monitor_stop`` are for
138 the event monitor enable and disable.
139 * ``rte_dev_event_callback_register`` and ``rte_dev_event_callback_unregister``
140 are for the user's callbacks register and unregister.
142 Linux uevent is supported as backend of this device event notification framework.
144 * **Added support for procinfo and pdump on eth vdev.**
146 For ethernet virtual devices (like tap, pcap, etc), with this feature, we can get
147 stats/xstats on shared memory from secondary process, and also pdump packets on
148 those virtual devices.
154 .. This section should contain API changes. Sample format:
156 * Add a short 1-2 sentence description of the API change. Use fixed width
157 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
160 This section is a comment. Do not overwrite or remove it.
161 Also, make sure to start the actual text at the margin.
162 =========================================================
164 * service cores: no longer marked as experimental.
166 The service cores functions are no longer marked as experimental, and have
167 become part of the normal DPDK API and ABI. Any future ABI changes will be
168 announced at least one release before the ABI change is made. There are no
169 ABI breaking changes planned.
171 * eal: ``rte_lcore_has_role()`` return value changed.
173 This function now returns true or false, respectively,
174 rather than 0 or <0 for success or failure.
175 It makes use of the function more intuitive.
177 * mempool: capability flags and related functions have been removed.
179 Flags ``MEMPOOL_F_CAPA_PHYS_CONTIG`` and
180 ``MEMPOOL_F_CAPA_BLK_ALIGNED_OBJECTS`` were used by octeontx mempool
181 driver to customize generic mempool library behaviour.
182 Now the new driver callbacks ``calc_mem_size`` and ``populate`` may be
183 used to achieve it without specific knowledge in the generic code.
185 * mempool: xmem functions have been deprecated:
187 - ``rte_mempool_xmem_create``
188 - ``rte_mempool_xmem_size``
189 - ``rte_mempool_xmem_usage``
190 - ``rte_mempool_populate_iova_tab``
192 * mbuf: The control mbuf API has been removed in v18.05. The impacted
193 functions and macros are:
195 - ``rte_ctrlmbuf_init()``
196 - ``rte_ctrlmbuf_alloc()``
197 - ``rte_ctrlmbuf_free()``
198 - ``rte_ctrlmbuf_data()``
199 - ``rte_ctrlmbuf_len()``
200 - ``rte_is_ctrlmbuf()``
203 The packet mbuf API should be used as a replacement.
205 * meter: updated to accommodate configuration profiles.
207 The meter API is changed to support meter configuration profiles. The
208 configuration profile represents the set of configuration parameters
209 for a given meter object, such as the rates and sizes for the token
210 buckets. These configuration parameters were previously the part of meter
211 object internal data strcuture. The separation of the configuration
212 parameters from meter object data structure results in reducing its
213 memory footprint which helps in better cache utilization when large number
214 of meter objects are used.
216 * ethdev: The function ``rte_eth_dev_count``, often mis-used to iterate
217 over ports, is deprecated and replaced by ``rte_eth_dev_count_avail``.
218 There is also a new function ``rte_eth_dev_count_total`` to get the
219 total number of allocated ports, available or not.
220 The hotplug-proof applications should use ``RTE_ETH_FOREACH_DEV`` or
221 ``RTE_ETH_FOREACH_DEV_OWNED_BY`` as port iterators.
223 * ethdev, in struct ``struct rte_eth_dev_info``, field ``rte_pci_device *pci_dev``
224 replaced with field ``struct rte_device *device``.
226 * **Changes to semantics of rte_eth_dev_configure() parameters.**
228 If both the ``nb_rx_q`` and ``nb_tx_q`` parameters are zero,
229 ``rte_eth_dev_configure`` will now use PMD-recommended queue sizes, or if
230 recommendations are not provided by the PMD the function will use ethdev
231 fall-back values. Previously setting both of the parameters to zero would
232 have resulted in ``-EINVAL`` being returned.
234 * **Changes to semantics of rte_eth_rx_queue_setup() parameters.**
236 If the ``nb_rx_desc`` parameter is zero, ``rte_eth_rx_queue_setup`` will
237 now use the PMD-recommended Rx ring size, or in the case where the PMD
238 does not provide a recommendation, will use an ethdev-provided
239 fall-back value. Previously, setting ``nb_rx_desc`` to zero would have
240 resulted in an error.
242 * **Changes to semantics of rte_eth_tx_queue_setup() parameters.**
244 If the ``nb_tx_desc`` parameter is zero, ``rte_eth_tx_queue_setup`` will
245 now use the PMD-recommended Tx ring size, or in the case where the PMD
246 does not provide a recoomendation, will use an ethdev-provided
247 fall-back value. Previously, setting ``nb_tx_desc`` to zero would have
248 resulted in an error.
254 .. This section should contain ABI changes. Sample format:
256 * Add a short 1-2 sentence description of the ABI change that was announced
257 in the previous releases and made in this release. Use fixed width quotes
258 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
260 This section is a comment. Do not overwrite or remove it.
261 Also, make sure to start the actual text at the margin.
262 =========================================================
264 * ring: the alignment constraints on the ring structure has been relaxed
265 to one cache line instead of two, and an empty cache line padding is
266 added between the producer and consumer structures. The size of the
267 structure and the offset of the fields remains the same on platforms
268 with 64B cache line, but change on other platforms.
270 * mempool: ops have changed.
272 A new callback ``calc_mem_size`` has been added to ``rte_mempool_ops``
273 to allow to customize required memory size calculation.
274 A new callback ``populate`` has been added to ``rte_mempool_ops``
275 to allow to customize objects population.
276 Callback ``get_capabilities`` has been removed from ``rte_mempool_ops``
277 since its features are covered by ``calc_mem_size`` and ``populate``
279 Callback ``register_memory_area`` has been removed from ``rte_mempool_ops``
280 since the new callback ``populate`` may be used instead of it.
282 * **Additional fields in rte_eth_dev_info.**
284 The ``rte_eth_dev_info`` structure has had two extra entries appended to the
285 end of it: ``default_rxportconf`` and ``default_txportconf``. Each of these
286 in turn are ``rte_eth_dev_portconf`` structures containing three fields of
287 type ``uint16_t``: ``burst_size``, ``ring_size``, and ``nb_queues``. These
288 are parameter values recommended for use by the PMD.
294 .. This section should contain removed items in this release. Sample format:
296 * Add a short 1-2 sentence description of the removed item in the past
299 This section is a comment. Do not overwrite or remove it.
300 Also, make sure to start the actual text at the margin.
301 =========================================================
307 .. This section should contain new known issues in this release. Sample format:
309 * **Add title in present tense with full stop.**
311 Add a short 1-2 sentence description of the known issue in the present
312 tense. Add information on any known workarounds.
314 This section is a comment. Do not overwrite or remove it.
315 Also, make sure to start the actual text at the margin.
316 =========================================================
318 * **pdump is not compatible with old applications.**
320 As we changed to use generic multi-process communication for pdump negotiation
321 instead of previous dedicated unix socket way, pdump applications, including
322 dpdk-pdump example and any other applications using librte_pdump, cannot work
323 with older version DPDK primary applications.
326 Shared Library Versions
327 -----------------------
329 .. Update any library version updated in this release and prepend with a ``+``
333 + librte_cfgfile.so.2
336 This section is a comment. Do not overwrite or remove it.
337 =========================================================
340 The libraries prepended with a plus sign were incremented in this version.
346 librte_bitratestats.so.2
348 librte_bus_fslmc.so.1
353 + librte_common_octeontx.so.1
354 librte_cryptodev.so.4
355 librte_distributor.so.1
359 librte_flow_classify.so.1
367 librte_latencystats.so.1
370 + librte_mempool.so.4
380 librte_pmd_ixgbe.so.2
382 librte_pmd_softnic.so.1
383 librte_pmd_vhost.so.2
399 .. This section should contain a list of platforms that were tested with this
404 * <vendor> platform with <vendor> <type of devices> combinations
409 * Other relevant details...
411 This section is a comment. Do not overwrite or remove it.
412 Also, make sure to start the actual text at the margin.
413 =========================================================