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
85 .. This section should contain bug fixes added to the relevant sections. Sample format:
87 * **code/section Fixed issue in the past tense with a full stop.**
89 Add a short 1-2 sentence description of the resolved issue in the past tense.
90 The title should contain the code/lib section like a commit message.
91 Add the entries in alphabetic order in the relevant sections below.
93 This section is a comment. do not overwrite or remove it.
94 Also, make sure to start the actual text at the margin.
95 =========================================================
105 * **net/virtio: Fixed multiple process support.**
107 Fixed few regressions introduced in recent releases that break the virtio
108 multiple process support.
118 * **examples/ethtool: Fixed crash with non-PCI devices.**
120 Querying a non-PCI device was dereferencing non-existent PCI data
121 resulting in a segmentation fault.
131 .. This section should contain new known issues in this release. Sample format:
133 * **Add title in present tense with full stop.**
135 Add a short 1-2 sentence description of the known issue in the present
136 tense. Add information on any known workarounds.
138 This section is a comment. do not overwrite or remove it.
139 Also, make sure to start the actual text at the margin.
140 =========================================================
146 .. This section should contain API changes. Sample format:
148 * Add a short 1-2 sentence description of the API change. Use fixed width
149 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
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 ABI changes. Sample format:
161 * Add a short 1-2 sentence description of the ABI change that was announced in
162 the previous releases and made in this release. Use fixed width quotes for
163 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
165 This section is a comment. do not overwrite or remove it.
166 Also, make sure to start the actual text at the margin.
167 =========================================================
171 Shared Library Versions
172 -----------------------
174 .. Update any library version updated in this release and prepend with a ``+``
178 + librte_cfgfile.so.2
181 This section is a comment. do not overwrite or remove it.
182 =========================================================
185 The libraries prepended with a plus sign were incremented in this version.
192 librte_cryptodev.so.2
193 librte_distributor.so.1
223 .. This section should contain a list of platforms that were tested with this release.
232 This section is a comment. do not overwrite or remove it.
233 Also, make sure to start the actual text at the margin.
234 =========================================================
240 .. This section should contain a list of NICs that were tested with this release.
249 This section is a comment. do not overwrite or remove it.
250 Also, make sure to start the actual text at the margin.
251 =========================================================
257 .. This section should contain a list of OSes that were tested with this release.
258 The format is as follows, in alphabetical order:
264 * Red Hat Enterprise Linux 7.2
265 * SUSE Enterprise Linux 12
270 This section is a comment. do not overwrite or remove it.
271 Also, make sure to start the actual text at the margin.
272 =========================================================