2016-04-12 12:55:10 +00:00
|
|
|
DPDK Release 16.07
|
|
|
|
|
==================
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. **Read this first.**
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
The text below explains how to update the release notes.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
Use proper spelling, capitalization and punctuation in all sections.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
Variable and config names should be quoted as fixed width text: ``LIKE_THIS``.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
Build the docs and view the output file to ensure the changes are correct::
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
make doc-guides-html
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
firefox build/doc/html/guides/rel_notes/release_16_07.html
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
New Features
|
|
|
|
|
------------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain new features added in this release. Sample format:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
* **Add a title in the past tense with a full stop.**
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
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.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
If the feature adds a lot of sub-features you can use a bullet list like this.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
* Added feature foo to do something.
|
|
|
|
|
* Enhanced feature bar to do something else.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
Refer to the previous release notes for examples.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-04-14 09:42:36 +00:00
|
|
|
* **Removed mempool cache if not needed.**
|
|
|
|
|
|
|
|
|
|
The size of the mempool structure is reduced if the per-lcore cache is disabled.
|
|
|
|
|
|
mempool: allow user-owned cache
The mempool cache is only available to EAL threads as a per-lcore
resource. Change this so that the user can create and provide their own
cache on mempool get and put operations. This works with non-EAL threads
too. This commit introduces the new API calls:
rte_mempool_cache_create(size, socket_id)
rte_mempool_cache_free(cache)
rte_mempool_cache_flush(cache, mp)
rte_mempool_default_cache(mp, lcore_id)
Changes the API calls:
rte_mempool_generic_put(mp, obj_table, n, cache, flags)
rte_mempool_generic_get(mp, obj_table, n, cache, flags)
The cache-oblivious API calls use the per-lcore default local cache.
Signed-off-by: Lazaros Koromilas <l@nofutznetworks.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
2016-06-28 23:47:38 +00:00
|
|
|
* **Added mempool external cache for non-EAL thread.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
Added new functions to create, free or flush a user-owned mempool
|
|
|
|
|
cache for non-EAL threads. Previously the cache was always disabled
|
|
|
|
|
on these threads.
|
mempool: allow user-owned cache
The mempool cache is only available to EAL threads as a per-lcore
resource. Change this so that the user can create and provide their own
cache on mempool get and put operations. This works with non-EAL threads
too. This commit introduces the new API calls:
rte_mempool_cache_create(size, socket_id)
rte_mempool_cache_free(cache)
rte_mempool_cache_flush(cache, mp)
rte_mempool_default_cache(mp, lcore_id)
Changes the API calls:
rte_mempool_generic_put(mp, obj_table, n, cache, flags)
rte_mempool_generic_get(mp, obj_table, n, cache, flags)
The cache-oblivious API calls use the per-lcore default local cache.
Signed-off-by: Lazaros Koromilas <l@nofutznetworks.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
2016-06-28 23:47:38 +00:00
|
|
|
|
2016-05-18 11:04:56 +00:00
|
|
|
* **Changed the memory allocation in mempool library.**
|
|
|
|
|
|
|
|
|
|
* Added ability to allocate a large mempool in virtually fragmented memory.
|
|
|
|
|
* Added new APIs to populate a mempool with memory.
|
|
|
|
|
* Added an API to free a mempool.
|
2016-07-19 13:16:35 +00:00
|
|
|
* Modified the API of the ``rte_mempool_obj_iter()`` function.
|
2016-05-18 11:04:56 +00:00
|
|
|
* Dropped specific Xen Dom0 code.
|
|
|
|
|
* Dropped specific anonymous mempool code in testpmd.
|
|
|
|
|
|
2016-06-15 21:23:01 +00:00
|
|
|
* **Added new driver for Broadcom NetXtreme-C devices.**
|
|
|
|
|
|
|
|
|
|
Added the new bnxt driver for Broadcom NetXtreme-C devices. See the
|
|
|
|
|
"Network Interface Controller Drivers" document for more details on this
|
|
|
|
|
new driver.
|
|
|
|
|
|
2016-06-17 13:29:53 +00:00
|
|
|
* **Added new driver for ThunderX nicvf device.**
|
|
|
|
|
|
2016-06-01 01:53:09 +00:00
|
|
|
* **Added mailbox interrupt support for ixgbe and igb VFs.**
|
2016-06-01 01:53:08 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
When the physical NIC link comes up or down, the PF driver will send a
|
2016-06-01 01:53:08 +00:00
|
|
|
mailbox message to notify each VF. To handle this link up/down event,
|
2016-07-19 13:16:35 +00:00
|
|
|
support have been added for a mailbox interrupt to receive the message and
|
|
|
|
|
allow the application to register a callback for it.
|
2016-06-01 01:53:08 +00:00
|
|
|
|
2016-06-23 07:22:37 +00:00
|
|
|
* **Updated the ixgbe base driver.**
|
|
|
|
|
|
|
|
|
|
The ixgbe base driver was updated with changes including the
|
|
|
|
|
following:
|
|
|
|
|
|
|
|
|
|
* Added sgmii link for X550.
|
2016-07-19 13:16:35 +00:00
|
|
|
* Added MAC link setup for X550a SFP and SFP+.
|
2016-06-23 07:22:37 +00:00
|
|
|
* Added KR support for X550em_a.
|
2016-07-19 13:16:35 +00:00
|
|
|
* Added new PHY definitions for M88E1500.
|
2016-06-23 07:22:37 +00:00
|
|
|
* Added support for the VLVF to be bypassed when adding/removing a VFTA entry.
|
|
|
|
|
* Added X550a flow control auto negotiation support.
|
|
|
|
|
|
2016-06-14 13:56:37 +00:00
|
|
|
* **Updated the i40e base driver.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
Updated the i40e base driver including support for new devices IDs.
|
2016-06-14 13:56:37 +00:00
|
|
|
|
2016-07-21 09:11:58 +00:00
|
|
|
* **Updated the enic driver.**
|
|
|
|
|
|
|
|
|
|
The enic driver was updated with changes including the following:
|
|
|
|
|
|
|
|
|
|
* Optimized the Tx function.
|
|
|
|
|
* Added Scattered Rx capability.
|
|
|
|
|
* Improved packet type identification.
|
|
|
|
|
* Added MTU update in non Scattered Rx mode and enabled MTU of up to 9208
|
|
|
|
|
with UCS Software release 2.2 on 1300 series VICs.
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* **Added support for virtio on IBM POWER8.**
|
2016-05-17 09:59:52 +00:00
|
|
|
|
|
|
|
|
The ioports are mapped in memory when using Linux UIO.
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* **Added support for Virtio in containers.**
|
net/virtio-user: add virtual device
Add a new virtual device named virtio-user, which can be used just like
eth_ring, eth_null, etc. To reuse the code of original virtio, we do
some adjustment in virtio_ethdev.c, such as remove key _static_ of
eth_virtio_dev_init() so that it can be reused in virtual device; and
we add some check to make sure it will not crash.
Configured parameters include:
- queues (optional, 1 by default), number of queue pairs, multi-queue
not supported for now.
- cq (optional, 0 by default), not supported for now.
- mac (optional), random value will be given if not specified.
- queue_size (optional, 256 by default), size of virtqueues.
- path (madatory), path of vhost user.
When enable CONFIG_RTE_VIRTIO_USER (enabled by default), the compiled
library can be used in both VM and container environment.
Examples:
path_vhost=<path_to_vhost_user> # use vhost-user as a backend
sudo ./examples/l2fwd/build/l2fwd -c 0x100000 -n 4 \
--socket-mem 0,1024 --no-pci --file-prefix=l2fwd \
--vdev=virtio-user0,mac=00:01:02:03:04:05,path=$path_vhost -- -p 0x1
Known issues:
- Control queue and multi-queue are not supported yet.
- Cannot work with --huge-unlink.
- Cannot work with no-huge.
- Cannot work when there are more than VHOST_MEMORY_MAX_NREGIONS(8)
hugepages.
- Root privilege is a must (mainly becase of sorting hugepages according
to physical address).
- Applications should not use file name like HUGEFILE_FMT ("%smap_%d").
- Cannot work with vhost-net backend.
Signed-off-by: Huawei Xie <huawei.xie@intel.com>
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-06-15 09:03:25 +00:00
|
|
|
|
2016-07-22 02:24:47 +00:00
|
|
|
Add a new virtual device, named virtio_user, to support virtio for containers.
|
net/virtio-user: add virtual device
Add a new virtual device named virtio-user, which can be used just like
eth_ring, eth_null, etc. To reuse the code of original virtio, we do
some adjustment in virtio_ethdev.c, such as remove key _static_ of
eth_virtio_dev_init() so that it can be reused in virtual device; and
we add some check to make sure it will not crash.
Configured parameters include:
- queues (optional, 1 by default), number of queue pairs, multi-queue
not supported for now.
- cq (optional, 0 by default), not supported for now.
- mac (optional), random value will be given if not specified.
- queue_size (optional, 256 by default), size of virtqueues.
- path (madatory), path of vhost user.
When enable CONFIG_RTE_VIRTIO_USER (enabled by default), the compiled
library can be used in both VM and container environment.
Examples:
path_vhost=<path_to_vhost_user> # use vhost-user as a backend
sudo ./examples/l2fwd/build/l2fwd -c 0x100000 -n 4 \
--socket-mem 0,1024 --no-pci --file-prefix=l2fwd \
--vdev=virtio-user0,mac=00:01:02:03:04:05,path=$path_vhost -- -p 0x1
Known issues:
- Control queue and multi-queue are not supported yet.
- Cannot work with --huge-unlink.
- Cannot work with no-huge.
- Cannot work when there are more than VHOST_MEMORY_MAX_NREGIONS(8)
hugepages.
- Root privilege is a must (mainly becase of sorting hugepages according
to physical address).
- Applications should not use file name like HUGEFILE_FMT ("%smap_%d").
- Cannot work with vhost-net backend.
Signed-off-by: Huawei Xie <huawei.xie@intel.com>
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-06-15 09:03:25 +00:00
|
|
|
|
|
|
|
|
Known limitations:
|
|
|
|
|
|
|
|
|
|
* Control queue and multi-queue are not supported yet.
|
2016-07-19 13:16:35 +00:00
|
|
|
* Doesn't work with ``--huge-unlink``.
|
|
|
|
|
* Doesn't work with ``--no-huge``.
|
|
|
|
|
* Doesn't work when there are more than ``VHOST_MEMORY_MAX_NREGIONS(8)`` hugepages.
|
|
|
|
|
* Root privilege is required for sorting hugepages by physical address.
|
|
|
|
|
* Can only be used with the vhost user backend.
|
net/virtio-user: add virtual device
Add a new virtual device named virtio-user, which can be used just like
eth_ring, eth_null, etc. To reuse the code of original virtio, we do
some adjustment in virtio_ethdev.c, such as remove key _static_ of
eth_virtio_dev_init() so that it can be reused in virtual device; and
we add some check to make sure it will not crash.
Configured parameters include:
- queues (optional, 1 by default), number of queue pairs, multi-queue
not supported for now.
- cq (optional, 0 by default), not supported for now.
- mac (optional), random value will be given if not specified.
- queue_size (optional, 256 by default), size of virtqueues.
- path (madatory), path of vhost user.
When enable CONFIG_RTE_VIRTIO_USER (enabled by default), the compiled
library can be used in both VM and container environment.
Examples:
path_vhost=<path_to_vhost_user> # use vhost-user as a backend
sudo ./examples/l2fwd/build/l2fwd -c 0x100000 -n 4 \
--socket-mem 0,1024 --no-pci --file-prefix=l2fwd \
--vdev=virtio-user0,mac=00:01:02:03:04:05,path=$path_vhost -- -p 0x1
Known issues:
- Control queue and multi-queue are not supported yet.
- Cannot work with --huge-unlink.
- Cannot work with no-huge.
- Cannot work when there are more than VHOST_MEMORY_MAX_NREGIONS(8)
hugepages.
- Root privilege is a must (mainly becase of sorting hugepages according
to physical address).
- Applications should not use file name like HUGEFILE_FMT ("%smap_%d").
- Cannot work with vhost-net backend.
Signed-off-by: Huawei Xie <huawei.xie@intel.com>
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-06-15 09:03:25 +00:00
|
|
|
|
2016-05-06 21:26:03 +00:00
|
|
|
* **Added vhost-user client mode.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
DPDK vhost-user now supports client mode as well as server mode. Client mode
|
|
|
|
|
is enabled when the ``RTE_VHOST_USER_CLIENT`` flag is set while calling
|
2016-05-06 21:26:03 +00:00
|
|
|
``rte_vhost_driver_register``.
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
When DPDK vhost-user restarts from an normal or abnormal exit (such as a
|
|
|
|
|
crash), the client mode allows DPDK to establish the connection again. Note
|
|
|
|
|
that QEMU version v2.7 or above is required for this feature.
|
2016-05-06 21:26:03 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
DPDK vhost-user will also try to reconnect by default when:
|
2016-05-12 23:14:19 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* The first connect fails (when QEMU is not started yet).
|
|
|
|
|
* The connection is broken (when QEMU restarts).
|
2016-05-12 23:14:19 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
It can be turned off by setting the ``RTE_VHOST_USER_NO_RECONNECT`` flag.
|
2016-05-12 23:14:19 +00:00
|
|
|
|
2016-05-03 05:51:12 +00:00
|
|
|
* **Added NSH packet recognition in i40e.**
|
|
|
|
|
|
2016-06-03 10:11:57 +00:00
|
|
|
* **Added AES-CTR support to AESNI MB PMD.**
|
|
|
|
|
|
|
|
|
|
Now AESNI MB PMD supports 128/192/256-bit counter mode AES encryption and
|
|
|
|
|
decryption.
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* **Added support for AES counter mode with Intel QuickAssist devices.**
|
2016-05-06 10:22:15 +00:00
|
|
|
|
|
|
|
|
Enabled support for the AES CTR algorithm for Intel QuickAssist devices.
|
|
|
|
|
Provided support for algorithm-chaining operations.
|
|
|
|
|
|
2016-06-20 14:40:04 +00:00
|
|
|
* **Added KASUMI SW PMD.**
|
|
|
|
|
|
|
|
|
|
A new Crypto PMD has been added, which provides KASUMI F8 (UEA1) ciphering
|
|
|
|
|
and KASUMI F9 (UIA1) hashing.
|
|
|
|
|
|
2016-06-16 22:14:14 +00:00
|
|
|
* **Added multi-writer support for RTE Hash with Intel TSX.**
|
|
|
|
|
|
|
|
|
|
The following features/modifications have been added to rte_hash library:
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* Enabled application developers to use an extra flag for ``rte_hash``
|
|
|
|
|
creation to specify default behavior (multi-thread safe/unsafe) with the
|
|
|
|
|
``rte_hash_add_key`` function.
|
|
|
|
|
* Changed the Cuckoo Hash Search algorithm to breadth first search for
|
|
|
|
|
multi-writer routines and split Cuckoo Hash Search and Move operations in
|
|
|
|
|
order to reduce transactional code region and improve TSX performance.
|
|
|
|
|
* Added a hash multi-writer test case to the test app.
|
2016-06-16 22:14:14 +00:00
|
|
|
|
2016-05-30 17:14:49 +00:00
|
|
|
* **Improved IP Pipeline Application.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
The following features have been added to the ip_pipeline application:
|
2016-05-30 17:14:49 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* Configure the MAC address in the routing pipeline and automatic route
|
2016-06-01 14:01:01 +00:00
|
|
|
updates with change in link state.
|
2016-05-30 17:14:49 +00:00
|
|
|
* Enable RSS per network interface through the configuration file.
|
|
|
|
|
* Streamline the CLI code.
|
|
|
|
|
|
2016-06-15 15:25:50 +00:00
|
|
|
* **Added keepalive enhancements.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
Added support for reporting of core states other than dead to
|
2016-06-15 15:25:50 +00:00
|
|
|
monitoring applications, enabling the support of broader liveness
|
|
|
|
|
reporting to external processes.
|
|
|
|
|
|
pdump: add new library for packet capture
The librte_pdump library provides a framework for
packet capturing in dpdk. The library provides set of
APIs to initialize the packet capture framework, to
enable or disable the packet capture, and to uninitialize
it.
The librte_pdump library works on a client/server model.
The server is responsible for enabling or disabling the
packet capture and the clients are responsible
for requesting the enabling or disabling of the packet
capture.
Enabling APIs are supported with port, queue, ring and
mempool parameters. Applications should pass on this information
to get the packets from the dpdk ports.
For enabling requests from applications, library creates the client
request containing the mempool, ring, port and queue information and
sends the request to the server. After receiving the request, server
registers the Rx and Tx callbacks for all the port and queues.
After the callbacks registration, registered callbacks will get the
Rx and Tx packets. Packets then will be copied to the new mbufs that
are allocated from the user passed mempool. These new mbufs then will
be enqueued to the application passed ring. Applications need to dequeue
the mbufs from the rings and direct them to the devices like
pcap vdev for viewing the packets outside of the dpdk
using the packet capture tools.
For disabling requests, library creates the client request containing
the port and queue information and sends the request to the server.
After receiving the request, server removes the Rx and Tx callback
for all the port and queues.
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:22 +00:00
|
|
|
* **Added packet capture framework.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* A new library ``librte_pdump`` is added to provide a packet capture API.
|
|
|
|
|
* A new ``app/pdump`` tool is added to demonstrate capture packets in DPDK.
|
pdump: add new library for packet capture
The librte_pdump library provides a framework for
packet capturing in dpdk. The library provides set of
APIs to initialize the packet capture framework, to
enable or disable the packet capture, and to uninitialize
it.
The librte_pdump library works on a client/server model.
The server is responsible for enabling or disabling the
packet capture and the clients are responsible
for requesting the enabling or disabling of the packet
capture.
Enabling APIs are supported with port, queue, ring and
mempool parameters. Applications should pass on this information
to get the packets from the dpdk ports.
For enabling requests from applications, library creates the client
request containing the mempool, ring, port and queue information and
sends the request to the server. After receiving the request, server
registers the Rx and Tx callbacks for all the port and queues.
After the callbacks registration, registered callbacks will get the
Rx and Tx packets. Packets then will be copied to the new mbufs that
are allocated from the user passed mempool. These new mbufs then will
be enqueued to the application passed ring. Applications need to dequeue
the mbufs from the rings and direct them to the devices like
pcap vdev for viewing the packets outside of the dpdk
using the packet capture tools.
For disabling requests, library creates the client request containing
the port and queue information and sends the request to the server.
After receiving the request, server removes the Rx and Tx callback
for all the port and queues.
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:22 +00:00
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-06-29 13:06:03 +00:00
|
|
|
* **Added floating VEB support for i40e PF driver.**
|
|
|
|
|
|
|
|
|
|
A "floating VEB" is a special Virtual Ethernet Bridge (VEB) which does not
|
|
|
|
|
have an upload port, but instead is used for switching traffic between
|
|
|
|
|
virtual functions (VFs) on a port.
|
|
|
|
|
|
|
|
|
|
For information on this feature, please see the "I40E Poll Mode Driver"
|
|
|
|
|
section of the "Network Interface Controller Drivers" document.
|
|
|
|
|
|
2016-07-19 15:09:28 +00:00
|
|
|
* **Added support for live migration of a VM with SRIOV VF.**
|
|
|
|
|
|
|
|
|
|
Live migration of a VM with Virtio and VF PMD's using the bonding PMD.
|
|
|
|
|
|
2016-06-29 13:06:03 +00:00
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
Resolved Issues
|
|
|
|
|
---------------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain bug fixes added to the relevant sections. Sample format:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
* **code/section Fixed issue in the past tense with a full stop.**
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
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.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
EAL
|
|
|
|
|
~~~
|
|
|
|
|
|
2016-07-05 15:00:52 +00:00
|
|
|
* **igb_uio: Fixed possible mmap failure for Linux >= 4.5.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
The mmaping of the iomem range of the PCI device fails for kernels that
|
|
|
|
|
enabled the ``CONFIG_IO_STRICT_DEVMEM`` option. The error seen by the
|
|
|
|
|
user is as similar to the following::
|
2016-07-05 15:00:52 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
EAL: pci_map_resource():
|
2016-07-05 15:00:52 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0):
|
|
|
|
|
Invalid argument (0xffffffffffffffff)
|
2016-07-05 15:00:52 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
The ``CONFIG_IO_STRICT_DEVMEM`` kernel option was introduced in Linux v4.5.
|
|
|
|
|
|
|
|
|
|
The issues was resolve by updating ``igb_uio`` to stop reserving PCI memory
|
|
|
|
|
resources. From the kernel point of view the iomem region looks like idle
|
|
|
|
|
and mmap works again. This matches the ``uio_pci_generic`` usage.
|
2016-07-05 15:00:52 +00:00
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
Drivers
|
|
|
|
|
~~~~~~~
|
|
|
|
|
|
2016-05-04 05:42:25 +00:00
|
|
|
* **i40e: Fixed vlan stripping from inner header.**
|
|
|
|
|
|
|
|
|
|
Previously, for tunnel packets, such as VXLAN/NVGRE, the vlan
|
|
|
|
|
tags of the inner header will be stripped without putting vlan
|
|
|
|
|
info to descriptor.
|
|
|
|
|
Now this issue is fixed by disabling vlan stripping from inner header.
|
|
|
|
|
|
2016-06-22 02:53:51 +00:00
|
|
|
* **i40e: Fixed the type issue of a single VLAN type.**
|
|
|
|
|
|
|
|
|
|
Currently, if a single VLAN header is added in a packet, it's treated
|
|
|
|
|
as inner VLAN. But generally, a single VLAN header is treated as the
|
|
|
|
|
outer VLAN header.
|
|
|
|
|
This issue is fixed by changing corresponding register for single VLAN.
|
|
|
|
|
|
2016-07-21 09:11:58 +00:00
|
|
|
* **enic: Fixed several issues when stopping then restarting ports and queues.**
|
|
|
|
|
|
|
|
|
|
Fixed several crashes related to stopping then restarting ports and queues.
|
|
|
|
|
Fixed possible crash when re-configuring the number of Rx queue descriptors.
|
|
|
|
|
|
|
|
|
|
* **enic: Fixed Rx data mis-alignment if mbuf data offset modified.**
|
|
|
|
|
|
|
|
|
|
Fixed possible Rx corruption when mbufs were returned to a pool with data
|
|
|
|
|
offset other than RTE_PKTMBUF_HEADROOM.
|
|
|
|
|
|
|
|
|
|
* **enic: Fixed Tx IP/UDP/TCP checksum offload and VLAN insertion.**
|
|
|
|
|
|
|
|
|
|
* **enic: Fixed Rx error and missed counters.**
|
|
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
Libraries
|
|
|
|
|
~~~~~~~~~
|
|
|
|
|
|
2016-05-18 14:41:03 +00:00
|
|
|
* **mbuf: Fixed refcnt update when detaching.**
|
|
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
Fix the ``rte_pktmbuf_detach()`` function to decrement the direct mbuf's
|
|
|
|
|
reference counter. The previous behavior was not to affect the reference
|
|
|
|
|
counter. This lead to a memory leak of the direct mbuf.
|
2016-05-18 14:41:03 +00:00
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
Examples
|
|
|
|
|
~~~~~~~~
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other
|
|
|
|
|
~~~~~
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Known Issues
|
|
|
|
|
------------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain new known issues in this release. Sample format:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
* **Add title in present tense with full stop.**
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
Add a short 1-2 sentence description of the known issue in the present
|
|
|
|
|
tense. Add information on any known workarounds.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
API Changes
|
|
|
|
|
-----------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain API changes. Sample format:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
* 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.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* The following counters are removed from the ``rte_eth_stats`` structure:
|
|
|
|
|
|
|
|
|
|
* ``ibadcrc``
|
|
|
|
|
* ``ibadlen``
|
|
|
|
|
* ``imcasts``
|
|
|
|
|
* ``fdirmatch``
|
|
|
|
|
* ``fdirmiss``
|
|
|
|
|
* ``tx_pause_xon``
|
|
|
|
|
* ``rx_pause_xon``
|
|
|
|
|
* ``tx_pause_xoff``
|
|
|
|
|
* ``rx_pause_xoff``
|
2016-04-15 09:01:51 +00:00
|
|
|
|
2016-06-15 15:25:33 +00:00
|
|
|
* The extended statistics are fetched by ids with ``rte_eth_xstats_get``
|
|
|
|
|
after a lookup by name ``rte_eth_xstats_get_names``.
|
|
|
|
|
|
2016-06-15 14:06:20 +00:00
|
|
|
* The function ``rte_eth_dev_info_get`` fill the new fields ``nb_rx_queues``
|
|
|
|
|
and ``nb_tx_queues`` in the structure ``rte_eth_dev_info``.
|
|
|
|
|
|
2016-05-10 22:46:24 +00:00
|
|
|
* The vhost function ``rte_vring_available_entries`` is renamed to
|
|
|
|
|
``rte_vhost_avail_entries``.
|
|
|
|
|
|
2016-06-13 09:55:49 +00:00
|
|
|
* All existing vhost APIs and callbacks with ``virtio_net`` struct pointer
|
2016-07-19 13:16:35 +00:00
|
|
|
as the parameter have been changed due to the ABI refactoring described
|
|
|
|
|
below. It is replaced by ``int vid``.
|
2016-06-13 09:55:49 +00:00
|
|
|
|
2016-06-13 11:52:12 +00:00
|
|
|
* The function ``rte_vhost_enqueue_burst`` no longer supports concurrent enqueuing
|
|
|
|
|
packets to the same queue.
|
|
|
|
|
|
2016-05-20 15:17:04 +00:00
|
|
|
* The function ``rte_eth_dev_set_mtu`` adds a new return value ``-EBUSY``, which
|
|
|
|
|
indicates the operation is forbidden because the port is running.
|
|
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
ABI Changes
|
|
|
|
|
-----------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. * 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.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* The ``rte_port_source_params`` structure has new fields to support PCAP files.
|
2016-04-14 17:15:13 +00:00
|
|
|
It was already in release 16.04 with ``RTE_NEXT_ABI`` flag.
|
|
|
|
|
|
2016-06-15 14:06:20 +00:00
|
|
|
* The ``rte_eth_dev_info`` structure has new fields ``nb_rx_queues`` and ``nb_tx_queues``
|
2016-07-19 13:16:35 +00:00
|
|
|
to support the number of queues configured by software.
|
2016-06-15 14:06:20 +00:00
|
|
|
|
2016-07-19 13:16:35 +00:00
|
|
|
* A Vhost ABI refactoring has been made: the ``virtio_net`` structure is no
|
|
|
|
|
longer exported directly to the application. Instead, a handle, ``vid``, has
|
|
|
|
|
been used to represent this structure internally.
|
2016-06-13 09:55:49 +00:00
|
|
|
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
Shared Library Versions
|
|
|
|
|
-----------------------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. Update any library version updated in this release and prepend with a ``+`` sign.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
The libraries prepended with a plus sign were incremented in this version.
|
|
|
|
|
|
|
|
|
|
.. code-block:: diff
|
|
|
|
|
|
2016-04-15 09:01:51 +00:00
|
|
|
+ libethdev.so.4
|
2016-04-12 12:55:10 +00:00
|
|
|
librte_acl.so.2
|
|
|
|
|
librte_cfgfile.so.2
|
|
|
|
|
librte_cmdline.so.2
|
2016-07-20 12:31:12 +00:00
|
|
|
librte_cryptodev.so.1
|
2016-04-12 12:55:10 +00:00
|
|
|
librte_distributor.so.1
|
|
|
|
|
librte_eal.so.2
|
|
|
|
|
librte_hash.so.2
|
|
|
|
|
librte_ip_frag.so.1
|
|
|
|
|
librte_ivshmem.so.1
|
|
|
|
|
librte_jobstats.so.1
|
|
|
|
|
librte_kni.so.2
|
|
|
|
|
librte_kvargs.so.1
|
|
|
|
|
librte_lpm.so.2
|
|
|
|
|
librte_mbuf.so.2
|
2016-04-14 09:42:36 +00:00
|
|
|
+ librte_mempool.so.2
|
2016-04-12 12:55:10 +00:00
|
|
|
librte_meter.so.1
|
2016-07-06 15:57:40 +00:00
|
|
|
librte_pdump.so.1
|
2016-04-12 12:55:10 +00:00
|
|
|
librte_pipeline.so.3
|
|
|
|
|
librte_pmd_bond.so.1
|
|
|
|
|
librte_pmd_ring.so.2
|
2016-04-14 17:15:13 +00:00
|
|
|
+ librte_port.so.3
|
2016-04-12 12:55:10 +00:00
|
|
|
librte_power.so.1
|
|
|
|
|
librte_reorder.so.1
|
|
|
|
|
librte_ring.so.1
|
|
|
|
|
librte_sched.so.1
|
|
|
|
|
librte_table.so.2
|
|
|
|
|
librte_timer.so.1
|
2016-06-13 09:55:49 +00:00
|
|
|
+ librte_vhost.so.3
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Tested Platforms
|
|
|
|
|
----------------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain a list of platforms that were tested with this
|
|
|
|
|
release.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
The format is:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
#. Platform name.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
- Platform details.
|
|
|
|
|
- Platform details.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Tested NICs
|
|
|
|
|
-----------
|
|
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
.. This section should contain a list of NICs that were tested with this release.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
The format is:
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
#. NIC name.
|
2016-04-12 12:55:10 +00:00
|
|
|
|
2016-05-13 13:27:59 +00:00
|
|
|
- NIC details.
|
|
|
|
|
- NIC details.
|
