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_16_11.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. Make sure to start the actual text at the margin.
40 * **Added software parser for packet type.**
42 * Added a new function ``rte_pktmbuf_read()`` to read the packet data from an
43 mbuf chain, linearizing if required.
44 * Added a new function ``rte_net_get_ptype()`` to parse an Ethernet packet
45 in an mbuf chain and retrieve its packet type by software.
46 * Added new functions ``rte_get_ptype_*()`` to dump a packet type as a string.
48 * **Added vhost-user indirect descriptors support.**
50 If indirect descriptor feature is negotiated, each packet sent by the guest
51 will take exactly one slot in the enqueue virtqueue. Without the feature, in
52 current version, even 64 bytes packets take two slots with Virtio PMD on guest
55 The main impact is better performance for 0% packet loss use-cases, as it
56 behaves as if the virtqueue size was enlarged, so more packets can be buffered
57 in case of system perturbations. On the downside, small performance degradation
58 is measured when running micro-benchmarks.
60 * **Added vhost PMD xstats.**
62 Added extended statistics to vhost PMD from per port perspective.
64 * **Added virtio NEON support for ARM.**
66 * **Updated the ixgbe base driver.**
68 Updated the ixgbe base driver, including the following changes:
70 * add X550em_a 10G PHY support
71 * support flow control auto negotiation for X550em_a 1G PHY
72 * add X550em_a FW ALEF support
73 * increase mailbox version to ixgbe_mbox_api_13
74 * add two MAC ops for Hyper-V support
76 * **Updated the QAT PMD.**
78 The QAT PMD was updated with following support:
81 * SHA224-HMAC algorithm
82 * SHA384-HMAC algorithm
84 * KASUMI (F8 and F9) algorithm
90 * **Added libcrypto PMD.**
92 A new crypto PMD has been added, which provides several ciphering and hashing.
93 All cryptography operations are using Openssl library crypto API.
95 * **Updated the IPsec example with following support:**
98 * AES CBC IV generation with cipher forward function
101 * **Added support for new gcc -march option.**
103 The GCC 4.9 ``-march`` option supports the Intel processor code names.
104 The config option ``RTE_MACHINE`` can be used to pass code names to the compiler as ``-march`` flag.
110 .. This section should contain bug fixes added to the relevant sections. Sample format:
112 * **code/section Fixed issue in the past tense with a full stop.**
114 Add a short 1-2 sentence description of the resolved issue in the past tense.
115 The title should contain the code/lib section like a commit message.
116 Add the entries in alphabetic order in the relevant sections below.
118 This section is a comment. Make sure to start the actual text at the margin.
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. Make sure to start the actual text at the margin.
157 .. This section should contain API changes. Sample format:
159 * Add a short 1-2 sentence description of the API change. Use fixed width
160 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
162 This section is a comment. Make sure to start the actual text at the margin.
164 * The driver names have been changed. It especially impacts ``--vdev`` arguments.
165 Examples: ``eth_pcap`` becomes ``net_pcap``
166 and ``cryptodev_aesni_mb_pmd`` becomes ``crypto_aesni_mb``.
168 * The log history is removed.
170 * The ``rte_ivshmem`` feature (including library and EAL code) has been removed
171 in 16.11 because it had some design issues which were not planned to be fixed.
173 * The ``file_name`` data type of ``struct rte_port_source_params`` and
174 ``struct rte_port_sink_params`` is changed from `char *`` to ``const char *``.
180 .. This section should contain ABI changes. Sample format:
182 * Add a short 1-2 sentence description of the ABI change that was announced in
183 the previous releases and made in this release. Use fixed width quotes for
184 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
186 This section is a comment. Make sure to start the actual text at the margin.
190 Shared Library Versions
191 -----------------------
193 .. Update any library version updated in this release and prepend with a ``+``
198 + librte_cfgfile.so.2
203 The libraries prepended with a plus sign were incremented in this version.
211 librte_cryptodev.so.1
212 librte_distributor.so.1
240 .. This section should contain a list of platforms that were tested with this release.
249 This section is a comment. Make sure to start the actual text at the margin.
255 .. This section should contain a list of NICs that were tested with this release.
264 This section is a comment. Make sure to start the actual text at the margin.
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. Make sure to start the actual text at the margin.