DPDK Release 16.11
==================
-.. **Read this first.**
-
- The text below explains how to update the release notes.
-
- Use proper spelling, capitalization and punctuation in all sections.
-
- Variable and config names should be quoted as fixed width text: ``LIKE_THIS``.
-
- Build the docs and view the output file to ensure the changes are correct::
-
- make doc-guides-html
-
- firefox build/doc/html/guides/rel_notes/release_16_11.html
-
-
New Features
------------
-.. This section should contain new features added in this release. Sample format:
-
- * **Add a title in the past tense with a full stop.**
-
- Add a short 1-2 sentence description in the past tense. The description
- should be enough to allow someone scanning the release notes to understand
- the new feature.
-
- If the feature adds a lot of sub-features you can use a bullet list like this.
-
- * Added feature foo to do something.
- * Enhanced feature bar to do something else.
-
- Refer to the previous release notes for examples.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
-
* **Added software parser for packet type.**
* Added a new function ``rte_pktmbuf_read()`` to read the packet data from an
the current version, even 64 bytes packets take two slots with Virtio PMD on guest
side.
- The main impact is better performance for 0% packet loss use-cases, as it
+ The main impact is better performance for 0% packet loss use cases, as it
behaves as if the virtqueue size was enlarged, so more packets can be buffered
in the case of system perturbations. On the downside, small performance degradations
were measured when running micro-benchmarks.
The config option ``RTE_MACHINE`` can be used to pass code names to the compiler via the ``-march`` flag.
-Resolved Issues
----------------
-
-.. This section should contain bug fixes added to the relevant sections. Sample format:
-
- * **code/section Fixed issue in the past tense with a full stop.**
-
- Add a short 1-2 sentence description of the resolved issue in the past tense.
- The title should contain the code/lib section like a commit message.
- Add the entries in alphabetic order in the relevant sections below.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
-
Drivers
~~~~~~~
* **enic: Fixed high driver overhead when servicing Rx queues beyond the first.**
-
Known Issues
------------
-.. This section should contain new known issues in this release. Sample format:
-
- * **Add title in present tense with full stop.**
-
- Add a short 1-2 sentence description of the known issue in the present
- tense. Add information on any known workarounds.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
* **L3fwd-power app does not work properly when Rx vector is enabled.**
The L3fwd-power app doesn't work properly with some drivers in vector mode
API Changes
-----------
-.. This section should contain API changes. Sample format:
-
- * Add a short 1-2 sentence description of the API change. Use fixed width
- quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
* The driver naming convention has been changed to make them more
consistent. It especially impacts ``--vdev`` arguments. For example
``eth_pcap`` becomes ``net_pcap`` and ``cryptodev_aesni_mb_pmd`` becomes
and ``rte_eal_vdrv_unregister``.
-ABI Changes
------------
-
-.. This section should contain ABI changes. Sample format:
-
- * Add a short 1-2 sentence description of the ABI change that was announced in
- the previous releases and made in this release. Use fixed width quotes for
- ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
-
-
Shared Library Versions
-----------------------
-.. Update any library version updated in this release and prepend with a ``+``
- sign, like this:
-
- libethdev.so.4
- librte_acl.so.2
- + librte_cfgfile.so.2
- librte_cmdline.so.2
-
-
-
The libraries prepended with a plus sign were incremented in this version.
.. code-block:: diff
Tested Platforms
----------------
-.. This section should contain a list of platforms that were tested with this release.
-
- The format is:
-
- #. Platform name.
-
- * Platform details.
- * Platform details.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
#. SuperMicro 1U
- BIOS: 1.0c
Tested NICs
-----------
-.. This section should contain a list of NICs that were tested with this release.
-
- The format is:
-
- #. NIC name.
-
- * NIC details.
- * NIC details.
-
- This section is a comment. Make sure to start the actual text at the margin.
-
#. Intel(R) Ethernet Controller X540-AT2
- Firmware version: 0x80000389
Tested OSes
-----------
-.. This section should contain a list of OSes that were tested with this release.
- The format is as follows, in alphabetical order:
-
- * CentOS 7.0
- * Fedora 23
- * Fedora 24
- * FreeBSD 10.3
- * Red Hat Enterprise Linux 7.2
- * SUSE Enterprise Linux 12
- * Ubuntu 15.10
- * Ubuntu 16.04 LTS
- * Wind River Linux 8
-
- This section is a comment. Make sure to start the actual text at the margin.
-
* CentOS 7.2
* Fedora 23
* Fedora 24
git.droids-corp.org / dpdk.git / blobdiff