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.
50 The number may be obtained using rte_mempool_ops_get_info() API.
51 Contiguous blocks may be allocated using rte_mempool_get_contig_blocks() API.
53 * **Added PMD-recommended Tx and Rx parameters**
55 Applications can now query drivers for device-tuned values of
56 ring sizes, burst sizes, and number of queues.
58 * **Added RSS hash and key update to CXGBE PMD.**
60 Support to update RSS hash and key has been added to CXGBE PMD.
62 * **Added CXGBE VF PMD.**
64 CXGBE VF Poll Mode Driver has been added to run DPDK over Chelsio
65 T5/T6 NIC VF instances.
67 * **Updated Solarflare network PMD.**
69 Updated the sfc_efx driver including the following changes:
71 * Added support for Solarflare XtremeScale X2xxx family adapters.
72 * Added support for NVGRE, VXLAN and GENEVE filters in flow API.
73 * Added support for DROP action in flow API.
74 * Added support for equal stride super-buffer Rx mode (X2xxx only).
75 * Added support for MARK and FLAG actions in flow API (X2xxx only).
77 * **Added Ethernet poll mode driver for AMD XGBE devices.**
79 Added the new ``axgbe`` ethernet poll mode driver for AMD XGBE devices.
80 See the :doc:`../nics/axgbe` nic driver guide for more details on this
83 * **Updated szedata2 PMD.**
85 Added support for new NFB-200G2QL card.
86 New API was introduced in the libsze2 library which the szedata2 PMD depends
87 on thus the new version of the library was needed.
88 New versions of the packages are available and the minimum required version
91 * **Added support for Broadcom NetXtreme-S (BCM58800) family of controllers (aka Stingray)**
93 The BCM58800 devices feature a NetXtreme E-Series advanced network controller, a high-performance
94 ARM CPU block, PCI Express (PCIe) Gen3 interfaces, key accelerators for compute offload and a high-
95 speed memory subsystem including L3 cache and DDR4 interfaces, all interconnected by a coherent
96 Network-on-chip (NOC) fabric.
98 The ARM CPU subsystem features eight ARMv8 Cortex-A72 CPUs at 3.0 GHz, arranged in a multi-cluster
101 * **Added IFCVF vDPA driver.**
103 Added IFCVF vDPA driver to support Intel FPGA 100G VF device. IFCVF works
104 as a HW vhost data path accelerator, it supports live migration and is
105 compatible with virtio 0.95 and 1.0. This driver registers ifcvf vDPA driver
106 to vhost lib, when virtio connected, with the help of the registered vDPA
107 driver the assigned VF gets configured to Rx/Tx directly to VM's virtio
110 * **Added support for virtio-user server mode.**
111 In a container environment if the vhost-user backend restarts, there's no way
112 for it to reconnect to virtio-user. To address this, support for server mode
113 is added. In this mode the socket file is created by virtio-user, which the
114 backend connects to. This means that if the backend restarts, it can reconnect
115 to virtio-user and continue communications.
117 * **Added crypto workload support to vhost library.**
119 New APIs are introduced in vhost library to enable virtio crypto support
120 including session creation/deletion handling and translating virtio-crypto
121 request into DPDK crypto operations. A sample application is also introduced.
123 * **Added virtio crypto PMD.**
125 Added a new poll mode driver for virtio crypto devices, which provides
126 AES-CBC ciphering and AES-CBC with HMAC-SHA1 algorithm-chaining. See the
127 :doc:`../cryptodevs/virtio` crypto driver guide for more details on
130 * **Added AMD CCP Crypto PMD.**
132 Added the new ``ccp`` crypto driver for AMD CCP devices. See the
133 :doc:`../cryptodevs/ccp` crypto driver guide for more details on
136 * **Updated AESNI MB PMD.**
138 The AESNI MB PMD has been updated with additional support for:
140 * AES-CMAC (128-bit key).
142 * **Added the Event Timer Adapter Library.**
144 The Event Timer Adapter Library extends the event-based model by introducing
145 APIs that allow applications to arm/cancel event timers that generate
146 timer expiry events. This new type of event is scheduled by an event device
147 along with existing types of events.
149 * **Added OcteonTx TIM Driver (Event timer adapter).**
151 The OcteonTx Timer block enables software to schedule events for a future
152 time, it is exposed to an application via Event timer adapter library.
154 See the :doc:`../eventdevs/octeontx` guide for more details
156 * **Added Event Crypto Adapter Library.**
158 Added the Event Crypto Adapter Library. This library extends the
159 event-based model by introducing APIs that allow applications to
160 enqueue/dequeue crypto operations to/from cryptodev as events scheduled
163 * **Added DPAA2 QDMA Driver (in rawdev).**
165 The DPAA2 QDMA is an implementation of the rawdev API, that provide means
166 to initiate a DMA transaction from CPU. The initiated DMA is performed
167 without CPU being involved in the actual DMA transaction.
169 See the :doc:`../rawdevs/dpaa2_qdma` guide for more details.
171 * **Added DPAA2 Command Interface Driver (in rawdev).**
173 The DPAA2 CMDIF is an implementation of the rawdev API, that provides
174 communication between the GPP and NXP's QorIQ based AIOP Block (Firmware).
175 Advanced IO Processor i.e. AIOP is clusters of programmable RISC engines
176 optimised for flexible networking and I/O operations. The communication
177 between GPP and AIOP is achieved via using DPCI devices exposed by MC for
178 GPP <--> AIOP interaction.
180 See the :doc:`../rawdevs/dpaa2_cmdif` guide for more details.
182 * **Added device event monitor framework.**
184 Added a general device event monitor framework at EAL, for device dynamic management.
185 Such as device hotplug awareness and actions adopted accordingly. The list of new APIs:
187 * ``rte_dev_event_monitor_start`` and ``rte_dev_event_monitor_stop`` are for
188 the event monitor enable and disable.
189 * ``rte_dev_event_callback_register`` and ``rte_dev_event_callback_unregister``
190 are for the user's callbacks register and unregister.
192 Linux uevent is supported as backend of this device event notification framework.
194 * **Added support for procinfo and pdump on eth vdev.**
196 For ethernet virtual devices (like tap, pcap, etc), with this feature, we can get
197 stats/xstats on shared memory from secondary process, and also pdump packets on
198 those virtual devices.
204 .. This section should contain API changes. Sample format:
206 * Add a short 1-2 sentence description of the API change. Use fixed width
207 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
210 This section is a comment. Do not overwrite or remove it.
211 Also, make sure to start the actual text at the margin.
212 =========================================================
214 * service cores: no longer marked as experimental.
216 The service cores functions are no longer marked as experimental, and have
217 become part of the normal DPDK API and ABI. Any future ABI changes will be
218 announced at least one release before the ABI change is made. There are no
219 ABI breaking changes planned.
221 * eal: ``rte_lcore_has_role()`` return value changed.
223 This function now returns true or false, respectively,
224 rather than 0 or <0 for success or failure.
225 It makes use of the function more intuitive.
227 * mempool: capability flags and related functions have been removed.
229 Flags ``MEMPOOL_F_CAPA_PHYS_CONTIG`` and
230 ``MEMPOOL_F_CAPA_BLK_ALIGNED_OBJECTS`` were used by octeontx mempool
231 driver to customize generic mempool library behaviour.
232 Now the new driver callbacks ``calc_mem_size`` and ``populate`` may be
233 used to achieve it without specific knowledge in the generic code.
235 * mempool: xmem functions have been deprecated:
237 - ``rte_mempool_xmem_create``
238 - ``rte_mempool_xmem_size``
239 - ``rte_mempool_xmem_usage``
240 - ``rte_mempool_populate_iova_tab``
242 * mbuf: The control mbuf API has been removed in v18.05. The impacted
243 functions and macros are:
245 - ``rte_ctrlmbuf_init()``
246 - ``rte_ctrlmbuf_alloc()``
247 - ``rte_ctrlmbuf_free()``
248 - ``rte_ctrlmbuf_data()``
249 - ``rte_ctrlmbuf_len()``
250 - ``rte_is_ctrlmbuf()``
253 The packet mbuf API should be used as a replacement.
255 * meter: updated to accommodate configuration profiles.
257 The meter API is changed to support meter configuration profiles. The
258 configuration profile represents the set of configuration parameters
259 for a given meter object, such as the rates and sizes for the token
260 buckets. These configuration parameters were previously the part of meter
261 object internal data strcuture. The separation of the configuration
262 parameters from meter object data structure results in reducing its
263 memory footprint which helps in better cache utilization when large number
264 of meter objects are used.
266 * ethdev: The function ``rte_eth_dev_count``, often mis-used to iterate
267 over ports, is deprecated and replaced by ``rte_eth_dev_count_avail``.
268 There is also a new function ``rte_eth_dev_count_total`` to get the
269 total number of allocated ports, available or not.
270 The hotplug-proof applications should use ``RTE_ETH_FOREACH_DEV`` or
271 ``RTE_ETH_FOREACH_DEV_OWNED_BY`` as port iterators.
273 * ethdev, in struct ``struct rte_eth_dev_info``, field ``rte_pci_device *pci_dev``
274 replaced with field ``struct rte_device *device``.
276 * **Changes to semantics of rte_eth_dev_configure() parameters.**
278 If both the ``nb_rx_q`` and ``nb_tx_q`` parameters are zero,
279 ``rte_eth_dev_configure`` will now use PMD-recommended queue sizes, or if
280 recommendations are not provided by the PMD the function will use ethdev
281 fall-back values. Previously setting both of the parameters to zero would
282 have resulted in ``-EINVAL`` being returned.
284 * **Changes to semantics of rte_eth_rx_queue_setup() parameters.**
286 If the ``nb_rx_desc`` parameter is zero, ``rte_eth_rx_queue_setup`` will
287 now use the PMD-recommended Rx ring size, or in the case where the PMD
288 does not provide a recommendation, will use an ethdev-provided
289 fall-back value. Previously, setting ``nb_rx_desc`` to zero would have
290 resulted in an error.
292 * **Changes to semantics of rte_eth_tx_queue_setup() parameters.**
294 If the ``nb_tx_desc`` parameter is zero, ``rte_eth_tx_queue_setup`` will
295 now use the PMD-recommended Tx ring size, or in the case where the PMD
296 does not provide a recoomendation, will use an ethdev-provided
297 fall-back value. Previously, setting ``nb_tx_desc`` to zero would have
298 resulted in an error.
300 * ethdev: several changes were made to the flow API.
302 * Unused DUP action was removed.
303 * Actions semantics in flow rules: list order now matters ("first
304 to last" instead of "all simultaneously"), repeated actions are now
305 all performed, and they do not individually have (non-)terminating
307 * Flow rules are now always terminating unless a PASSTHRU action is
309 * C99-style flexible arrays were replaced with standard pointers in RSS
310 action and in RAW pattern item structures due to compatibility issues.
311 * The RSS action was modified to not rely on external
312 ``struct rte_eth_rss_conf`` anymore to instead expose its own and more
313 appropriately named configuration fields directly
314 (``rss_conf->rss_key`` => ``key``,
315 ``rss_conf->rss_key_len`` => ``key_len``,
316 ``rss_conf->rss_hf`` => ``types``,
317 ``num`` => ``queue_num``), and the addition of missing RSS parameters
318 (``func`` for RSS hash function to apply and ``level`` for the
319 encapsulation level).
320 * The VLAN pattern item (``struct rte_flow_item_vlan``) was modified to
321 include inner EtherType instead of outer TPID. Its default mask was also
322 modified to cover the VID part (lower 12 bits) of TCI only.
323 * A new transfer attribute was added to ``struct rte_flow_attr`` in order
324 to clarify the behavior of some pattern items.
325 * PF and VF pattern items are now only accepted by PMDs that implement
326 them (bnxt and i40e) when the transfer attribute is also present for
328 * Pattern item PORT was renamed PHY_PORT to avoid confusion with DPDK port
330 * An action counterpart to the PHY_PORT pattern item was added in order to
331 redirect matching traffic to a specific physical port.
332 * PORT_ID pattern item and actions were added to match and target DPDK
333 port IDs at a higher level than PHY_PORT.
335 * ethdev: change flow APIs regarding count action:
336 * ``rte_flow_create()`` API count action now requires the ``struct rte_flow_action_count``.
337 * ``rte_flow_query()`` API parameter changed from action type to action structure.
343 .. This section should contain ABI changes. Sample format:
345 * Add a short 1-2 sentence description of the ABI change that was announced
346 in the previous releases and made in this release. Use fixed width quotes
347 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
349 This section is a comment. Do not overwrite or remove it.
350 Also, make sure to start the actual text at the margin.
351 =========================================================
353 * ring: the alignment constraints on the ring structure has been relaxed
354 to one cache line instead of two, and an empty cache line padding is
355 added between the producer and consumer structures. The size of the
356 structure and the offset of the fields remains the same on platforms
357 with 64B cache line, but change on other platforms.
359 * mempool: ops have changed.
361 A new callback ``calc_mem_size`` has been added to ``rte_mempool_ops``
362 to allow to customize required memory size calculation.
363 A new callback ``populate`` has been added to ``rte_mempool_ops``
364 to allow to customize objects population.
365 Callback ``get_capabilities`` has been removed from ``rte_mempool_ops``
366 since its features are covered by ``calc_mem_size`` and ``populate``
368 Callback ``register_memory_area`` has been removed from ``rte_mempool_ops``
369 since the new callback ``populate`` may be used instead of it.
371 * **Additional fields in rte_eth_dev_info.**
373 The ``rte_eth_dev_info`` structure has had two extra entries appended to the
374 end of it: ``default_rxportconf`` and ``default_txportconf``. Each of these
375 in turn are ``rte_eth_dev_portconf`` structures containing three fields of
376 type ``uint16_t``: ``burst_size``, ``ring_size``, and ``nb_queues``. These
377 are parameter values recommended for use by the PMD.
379 * ethdev: ABI for all flow API functions was updated.
381 This includes functions ``rte_flow_copy``, ``rte_flow_create``,
382 ``rte_flow_destroy``, ``rte_flow_error_set``, ``rte_flow_flush``,
383 ``rte_flow_isolate``, ``rte_flow_query`` and ``rte_flow_validate``, due to
384 changes in error type definitions (``enum rte_flow_error_type``), removal
385 of the unused DUP action (``enum rte_flow_action_type``), modified
386 behavior for flow rule actions (see API changes), removal of C99 flexible
387 array from RAW pattern item (``struct rte_flow_item_raw``), complete
388 rework of the RSS action definition (``struct rte_flow_action_rss``),
389 sanity fix in the VLAN pattern item (``struct rte_flow_item_vlan``) and
390 new transfer attribute (``struct rte_flow_attr``).
396 .. This section should contain removed items in this release. Sample format:
398 * Add a short 1-2 sentence description of the removed item in the past
401 This section is a comment. Do not overwrite or remove it.
402 Also, make sure to start the actual text at the margin.
403 =========================================================
409 .. This section should contain new known issues in this release. Sample format:
411 * **Add title in present tense with full stop.**
413 Add a short 1-2 sentence description of the known issue in the present
414 tense. Add information on any known workarounds.
416 This section is a comment. Do not overwrite or remove it.
417 Also, make sure to start the actual text at the margin.
418 =========================================================
420 * **pdump is not compatible with old applications.**
422 As we changed to use generic multi-process communication for pdump negotiation
423 instead of previous dedicated unix socket way, pdump applications, including
424 dpdk-pdump example and any other applications using librte_pdump, cannot work
425 with older version DPDK primary applications.
428 Shared Library Versions
429 -----------------------
431 .. Update any library version updated in this release and prepend with a ``+``
435 + librte_cfgfile.so.2
438 This section is a comment. Do not overwrite or remove it.
439 =========================================================
442 The libraries prepended with a plus sign were incremented in this version.
448 librte_bitratestats.so.2
450 librte_bus_fslmc.so.1
455 + librte_common_octeontx.so.1
456 librte_cryptodev.so.4
457 librte_distributor.so.1
461 librte_flow_classify.so.1
469 librte_latencystats.so.1
472 + librte_mempool.so.4
482 librte_pmd_ixgbe.so.2
483 + librte_pmd_dpaa2_cmdif.so.1
484 + librte_pmd_dpaa2_qdma.so.1
486 librte_pmd_softnic.so.1
487 librte_pmd_vhost.so.2
503 .. This section should contain a list of platforms that were tested with this
508 * <vendor> platform with <vendor> <type of devices> combinations
513 * Other relevant details...
515 This section is a comment. Do not overwrite or remove it.
516 Also, make sure to start the actual text at the margin.
517 =========================================================