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 flow API (rte_flow).**
43 This API provides a generic means to configure hardware to match specific
44 ingress or egress traffic, alter its fate and query related counters
45 according to any number of user-defined rules.
47 It is slightly higher-level than the legacy filtering framework which it
48 encompasses and supersedes (including all functions and filter types) in
49 order to expose a single interface with an unambiguous behavior that is
50 common to all poll-mode drivers (PMDs).
52 See the :ref:`Generic flow API <Generic_flow_API>` documentation for more
55 * **Added APIs for MACsec offload support to the ixgbe PMD.**
57 Six new APIs have been added to the ixgbe PMD for MACsec offload support.
58 The declarations for the APIs can be found in ``rte_pmd_ixgbe.h``.
60 * **virtio-user with vhost-kernel as another exceptional path.**
62 Previously, we upstreamed a virtual device, virtio-user with vhost-user
63 as the backend, as a way for IPC (Inter-Process Communication) and user
64 space container networking.
66 Virtio-user with vhost-kernel as the backend is a solution for exceptional
67 path, such as KNI, which exchanges packets with kernel networking stack.
68 This solution is very promising in:
70 * maintenance: vhost and vhost-net (kernel) is upstreamed and extensively
72 * features: vhost-net is born to be a networking solution, which has
73 lots of networking related features, like multi-queue, TSO, multi-seg
75 * performance: similar to KNI, this solution would use one or more
76 kthreads to send/receive packets from user space DPDK applications,
77 which has little impact on user space polling thread (except that
78 it might enter into kernel space to wake up those kthreads if
81 * **Added virtio Rx interrupt suppprt.**
83 This feature enables Rx interrupt mode for virtio pci net devices as
84 binded to VFIO (noiommu mode) and drived by virtio PMD.
86 With this feature, virtio PMD can switch between polling mode and
87 interrupt mode, to achieve best performance, and at the same time save
88 power. It can work on both legacy and modern virtio devices. At this mode,
89 each rxq is mapped with an exluded MSIx interrupt.
91 See the :ref:`Virtio Interrupt Mode <virtio_interrupt_mode>` documentation
98 .. This section should contain bug fixes added to the relevant sections. Sample format:
100 * **code/section Fixed issue in the past tense with a full stop.**
102 Add a short 1-2 sentence description of the resolved issue in the past tense.
103 The title should contain the code/lib section like a commit message.
104 Add the entries in alphabetic order in the relevant sections below.
106 This section is a comment. do not overwrite or remove it.
107 Also, make sure to start the actual text at the margin.
108 =========================================================
118 * **net/virtio: Fixed multiple process support.**
120 Fixed few regressions introduced in recent releases that break the virtio
121 multiple process support.
131 * **examples/ethtool: Fixed crash with non-PCI devices.**
133 Querying a non-PCI device was dereferencing non-existent PCI data
134 resulting in a segmentation fault.
144 .. This section should contain new known issues in this release. Sample format:
146 * **Add title in present tense with full stop.**
148 Add a short 1-2 sentence description of the known issue in the present
149 tense. Add information on any known workarounds.
151 This section is a comment. do not overwrite or remove it.
152 Also, make sure to start the actual text at the margin.
153 =========================================================
159 .. This section should contain API changes. Sample format:
161 * Add a short 1-2 sentence description of the API change. Use fixed width
162 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
164 This section is a comment. do not overwrite or remove it.
165 Also, make sure to start the actual text at the margin.
166 =========================================================
172 .. This section should contain ABI changes. Sample format:
174 * Add a short 1-2 sentence description of the ABI change that was announced in
175 the previous releases and made in this release. Use fixed width quotes for
176 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
178 This section is a comment. do not overwrite or remove it.
179 Also, make sure to start the actual text at the margin.
180 =========================================================
184 Shared Library Versions
185 -----------------------
187 .. Update any library version updated in this release and prepend with a ``+``
191 + librte_cfgfile.so.2
194 This section is a comment. do not overwrite or remove it.
195 =========================================================
198 The libraries prepended with a plus sign were incremented in this version.
205 librte_cryptodev.so.2
206 librte_distributor.so.1
236 .. This section should contain a list of platforms that were tested with this release.
245 This section is a comment. do not overwrite or remove it.
246 Also, make sure to start the actual text at the margin.
247 =========================================================
253 .. This section should contain a list of NICs that were tested with this release.
262 This section is a comment. do not overwrite or remove it.
263 Also, make sure to start the actual text at the margin.
264 =========================================================
270 .. This section should contain a list of OSes that were tested with this release.
271 The format is as follows, in alphabetical order:
277 * Red Hat Enterprise Linux 7.2
278 * SUSE Enterprise Linux 12
283 This section is a comment. do not overwrite or remove it.
284 Also, make sure to start the actual text at the margin.
285 =========================================================