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 PMD-recommended Tx and Rx parameters**
46 Applications can now query drivers for device-tuned values of
47 ring sizes, burst sizes, and number of queues.
49 * **Added RSS hash and key update to CXGBE PMD.**
51 Support to update RSS hash and key has been added to CXGBE PMD.
53 * **Added CXGBE VF PMD.**
55 CXGBE VF Poll Mode Driver has been added to run DPDK over Chelsio
56 T5/T6 NIC VF instances.
58 * **Updated Solarflare network PMD.**
60 Updated the sfc_efx driver including the following changes:
62 * Added support for Solarflare XtremeScale X2xxx family adapters.
63 * Added support for NVGRE, VXLAN and GENEVE filters in flow API.
64 * Added support for DROP action in flow API.
66 * **Added Ethernet poll mode driver for AMD XGBE devices.**
68 Added the new ``axgbe`` ethernet poll mode driver for AMD XGBE devices.
69 See the :doc:`../nics/axgbe` nic driver guide for more details on this
72 * **Updated szedata2 PMD.**
74 Added support for new NFB-200G2QL card.
76 * **Added support for Broadcom NetXtreme-S (BCM58800) family of controllers (aka Stingray)**
78 The BCM58800 devices feature a NetXtreme E-Series advanced network controller, a high-performance
79 ARM CPU block, PCI Express (PCIe) Gen3 interfaces, key accelerators for compute offload and a high-
80 speed memory subsystem including L3 cache and DDR4 interfaces, all interconnected by a coherent
81 Network-on-chip (NOC) fabric.
83 The ARM CPU subsystem features eight ARMv8 Cortex-A72 CPUs at 3.0 GHz, arranged in a multi-cluster
86 * **Added support for virtio-user server mode.**
87 In a container environment if the vhost-user backend restarts, there's no way
88 for it to reconnect to virtio-user. To address this, support for server mode
89 is added. In this mode the socket file is created by virtio-user, which the
90 backend connects to. This means that if the backend restarts, it can reconnect
91 to virtio-user and continue communications.
93 * **Added crypto workload support to vhost library.**
95 New APIs are introduced in vhost library to enable virtio crypto support
96 including session creation/deletion handling and translating virtio-crypto
97 request into DPDK crypto operations. A sample application is also introduced.
99 * **Added the Event Timer Adapter Library.**
101 The Event Timer Adapter Library extends the event-based model by introducing
102 APIs that allow applications to arm/cancel event timers that generate
103 timer expiry events. This new type of event is scheduled by an event device
104 along with existing types of events.
106 * **Added device event monitor framework.**
108 Added a general device event monitor framework at EAL, for device dynamic management.
109 Such as device hotplug awareness and actions adopted accordingly. The list of new APIs:
111 * ``rte_dev_event_monitor_start`` and ``rte_dev_event_monitor_stop`` are for
112 the event monitor enable and disable.
113 * ``rte_dev_event_callback_register`` and ``rte_dev_event_callback_unregister``
114 are for the user's callbacks register and unregister.
116 Linux uevent is supported as backend of this device event notification framework.
122 .. This section should contain API changes. Sample format:
124 * Add a short 1-2 sentence description of the API change. Use fixed width
125 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
128 This section is a comment. Do not overwrite or remove it.
129 Also, make sure to start the actual text at the margin.
130 =========================================================
132 * mbuf: The control mbuf API has been removed in v18.05. The impacted
133 functions and macros are:
135 - ``rte_ctrlmbuf_init()``
136 - ``rte_ctrlmbuf_alloc()``
137 - ``rte_ctrlmbuf_free()``
138 - ``rte_ctrlmbuf_data()``
139 - ``rte_ctrlmbuf_len()``
140 - ``rte_is_ctrlmbuf()``
143 The packet mbuf API should be used as a replacement.
145 * meter: updated to accommodate configuration profiles.
147 The meter API is changed to support meter configuration profiles. The
148 configuration profile represents the set of configuration parameters
149 for a given meter object, such as the rates and sizes for the token
150 buckets. These configuration parameters were previously the part of meter
151 object internal data strcuture. The separation of the configuration
152 parameters from meter object data structure results in reducing its
153 memory footprint which helps in better cache utilization when large number
154 of meter objects are used.
156 * ethdev, in struct ``struct rte_eth_dev_info``, field ``rte_pci_device *pci_dev``
157 replaced with field ``struct rte_device *device``.
159 * **Changes to semantics of rte_eth_dev_configure() parameters.**
161 If both the ``nb_rx_q`` and ``nb_tx_q`` parameters are zero,
162 ``rte_eth_dev_configure`` will now use PMD-recommended queue sizes, or if
163 recommendations are not provided by the PMD the function will use ethdev
164 fall-back values. Previously setting both of the parameters to zero would
165 have resulted in ``-EINVAL`` being returned.
167 * **Changes to semantics of rte_eth_rx_queue_setup() parameters.**
169 If the ``nb_rx_desc`` parameter is zero, ``rte_eth_rx_queue_setup`` will
170 now use the PMD-recommended Rx ring size, or in the case where the PMD
171 does not provide a recommendation, will use an ethdev-provided
172 fall-back value. Previously, setting ``nb_rx_desc`` to zero would have
173 resulted in an error.
175 * **Changes to semantics of rte_eth_tx_queue_setup() parameters.**
177 If the ``nb_tx_desc`` parameter is zero, ``rte_eth_tx_queue_setup`` will
178 now use the PMD-recommended Tx ring size, or in the case where the PMD
179 does not provide a recoomendation, will use an ethdev-provided
180 fall-back value. Previously, setting ``nb_tx_desc`` to zero would have
181 resulted in an error.
187 .. This section should contain ABI changes. Sample format:
189 * Add a short 1-2 sentence description of the ABI change that was announced
190 in the previous releases and made in this release. Use fixed width quotes
191 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
193 This section is a comment. Do not overwrite or remove it.
194 Also, make sure to start the actual text at the margin.
195 =========================================================
197 * **Additional fields in rte_eth_dev_info.**
199 The ``rte_eth_dev_info`` structure has had two extra entries appended to the
200 end of it: ``default_rxportconf`` and ``default_txportconf``. Each of these
201 in turn are ``rte_eth_dev_portconf`` structures containing three fields of
202 type ``uint16_t``: ``burst_size``, ``ring_size``, and ``nb_queues``. These
203 are parameter values recommended for use by the PMD.
208 .. This section should contain removed items in this release. Sample format:
210 * Add a short 1-2 sentence description of the removed item in the past
213 This section is a comment. Do not overwrite or remove it.
214 Also, make sure to start the actual text at the margin.
215 =========================================================
221 .. This section should contain new known issues in this release. Sample format:
223 * **Add title in present tense with full stop.**
225 Add a short 1-2 sentence description of the known issue in the present
226 tense. Add information on any known workarounds.
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 =========================================================
233 Shared Library Versions
234 -----------------------
236 .. Update any library version updated in this release and prepend with a ``+``
240 + librte_cfgfile.so.2
243 This section is a comment. Do not overwrite or remove it.
244 =========================================================
247 The libraries prepended with a plus sign were incremented in this version.
253 librte_bitratestats.so.2
255 librte_bus_fslmc.so.1
260 + librte_common_octeontx.so.1
261 librte_cryptodev.so.4
262 librte_distributor.so.1
266 librte_flow_classify.so.1
274 librte_latencystats.so.1
287 librte_pmd_ixgbe.so.2
289 librte_pmd_softnic.so.1
290 librte_pmd_vhost.so.2
306 .. This section should contain a list of platforms that were tested with this
311 * <vendor> platform with <vendor> <type of devices> combinations
316 * Other relevant details...
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 =========================================================