d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
13726648ea
numam-dpdk/doc/guides/rel_notes/release_16_07.rst

430 lines
14 KiB
ReStructuredText
Raw Normal View History

doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
DPDK Release 16.07
==================
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. **Read this first.**
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
The text below explains how to update the release notes.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
Use proper spelling, capitalization and punctuation in all sections.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
Variable and config names should be quoted as fixed width text: ``LIKE_THIS``.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
Build the docs and view the output file to ensure the changes are correct::
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
make doc-guides-html
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
firefox build/doc/html/guides/rel_notes/release_16_07.html
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
New Features
------------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain new features added in this release. Sample format:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
* **Add a title in the past tense with a full stop.**
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
* Added feature foo to do something.
* Enhanced feature bar to do something else.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
Refer to the previous release notes for examples.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
mempool: reduce structure size if no cache needed The rte_mempool structure is changed, which will cause an ABI change for this structure. Providing backward compat is not reasonable here as this structure is used in multiple defines/inlines. Allow mempool cache support to be dynamic depending on if the mempool being created needs cache support. Saves about 1.5M of memory used by the rte_mempool structure. Allocating small mempools which do not require cache can consume larges amounts of memory if you have a number of these mempools. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
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.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
doc: update release notes about mempool allocation Remove the deprecation notice and add an entry in the release note for the changes in mempool allocation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
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.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* Modified the API of the ``rte_mempool_obj_iter()`` function.
doc: update release notes about mempool allocation Remove the deprecation notice and add an entry in the release note for the changes in mempool allocation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2016-05-18 11:04:56 +00:00
* Dropped specific Xen Dom0 code.
* Dropped specific anonymous mempool code in testpmd.
net/bnxt: add driver for Broadcom NetXtreme-C devices This patch adds the initial skeleton for bnxt driver along with the nic guide, and ties the driver into the build system. At this point, the driver simply fails init. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com> [Release Note Addition] Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
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.
doc: add ThunderX nicvf Updated doc/guides/nics/overview.rst, doc/guides/nics/thunderx.rst and release notes Changed "*" to "P" in overview.rst to capture the partially supported feature as "*" creating alignment issues with Sphinx table Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Slawomir Rosek <slawomir.rosek@semihalf.com> Signed-off-by: Maciej Czekaj <maciej.czekaj@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-06-17 13:29:53 +00:00
* **Added new driver for ThunderX nicvf device.**
net/igb: support VF mailbox interrupt for link up/down When using kernel PF and DPDK VF, when the PF driver finds the link state changes, up -> down or down -> up, the driver will send a message to VF by mailbox. This link state change may be triggered by PHY disconnection/reconnection, user config change like *ifconfig down/up* or interface parameter, like MTU change. This patch enables the support of the mailbox interrupt, so VF driver can receive the message for link up/down. After VF receives this message, VF port need to be reset to recover. This needs to be handled by the application so this patch allows the app to register a reset callback so it can reset the VF port. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
2016-06-01 01:53:09 +00:00
* **Added mailbox interrupt support for ixgbe and igb VFs.**
net/ixgbe: support VF mailbox interrupt for link up/down When using kernel PF and DPDK VF, when the PF driver finds the link state changes, up -> down or down -> up, the driver will send a message to VF by mailbox. This link state change may be triggered by PHY disconnection/reconnection, user config change like *ifconfig down/up* or interface parameter, like MTU change. This patch enables the support of the mailbox interrupt, so VF driver can receive the message for link up/down. After VF receives this message, VF port need to be reset to recover. This needs to be handled by the application so this patch allows the app to register a reset callback so it can reset the VF port. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
2016-06-01 01:53:08 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
When the physical NIC link comes up or down, the PF driver will send a
net/ixgbe: support VF mailbox interrupt for link up/down When using kernel PF and DPDK VF, when the PF driver finds the link state changes, up -> down or down -> up, the driver will send a message to VF by mailbox. This link state change may be triggered by PHY disconnection/reconnection, user config change like *ifconfig down/up* or interface parameter, like MTU change. This patch enables the support of the mailbox interrupt, so VF driver can receive the message for link up/down. After VF receives this message, VF port need to be reset to recover. This needs to be handled by the application so this patch allows the app to register a reset callback so it can reset the VF port. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
2016-06-01 01:53:08 +00:00
mailbox message to notify each VF. To handle this link up/down event,
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
net/ixgbe: support VF mailbox interrupt for link up/down When using kernel PF and DPDK VF, when the PF driver finds the link state changes, up -> down or down -> up, the driver will send a message to VF by mailbox. This link state change may be triggered by PHY disconnection/reconnection, user config change like *ifconfig down/up* or interface parameter, like MTU change. This patch enables the support of the mailbox interrupt, so VF driver can receive the message for link up/down. After VF receives this message, VF port need to be reset to recover. This needs to be handled by the application so this patch allows the app to register a reset callback so it can reset the VF port. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
2016-06-01 01:53:08 +00:00
net/ixgbe/base: update documentation for base code update The ixgbe base driver was updated to version cid-10g-shared-code.2016.04.12 The changes include: Added sgmii link for X550. Added mac link setup for X550a SFP and SFP+. Added KR support for X550em_a. Added new phy definitions for M88E1500. Added support for the VLVF to be bypassed when adding/removing a VFTA entry. Added X550a flow control auto negotiation support. Signed-off-by: Beilei Xing <beilei.xing@intel.com>
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.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* Added MAC link setup for X550a SFP and SFP+.
net/ixgbe/base: update documentation for base code update The ixgbe base driver was updated to version cid-10g-shared-code.2016.04.12 The changes include: Added sgmii link for X550. Added mac link setup for X550a SFP and SFP+. Added KR support for X550em_a. Added new phy definitions for M88E1500. Added support for the VLVF to be bypassed when adding/removing a VFTA entry. Added X550a flow control auto negotiation support. Signed-off-by: Beilei Xing <beilei.xing@intel.com>
2016-06-23 07:22:37 +00:00
* Added KR support for X550em_a.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* Added new PHY definitions for M88E1500.
net/ixgbe/base: update documentation for base code update The ixgbe base driver was updated to version cid-10g-shared-code.2016.04.12 The changes include: Added sgmii link for X550. Added mac link setup for X550a SFP and SFP+. Added KR support for X550em_a. Added new phy definitions for M88E1500. Added support for the VLVF to be bypassed when adding/removing a VFTA entry. Added X550a flow control auto negotiation support. Signed-off-by: Beilei Xing <beilei.xing@intel.com>
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.
net/i40e/base: document latest base code version Update the documentation and comments with brief details on the base code version included in this release. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-06-14 13:56:37 +00:00
* **Updated the i40e base driver.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
Updated the i40e base driver including support for new devices IDs.
net/i40e/base: document latest base code version Update the documentation and comments with brief details on the base code version included in this release. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-06-14 13:56:37 +00:00
doc: update release notes and guide for enic Signed-off-by: John Daley <johndale@cisco.com>
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.
doc: update guide and release notes for mlx5 Signed-off-by: Olga Shern <olgas@mellanox.com> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-07-27 09:27:26 +00:00
* **Updated the mlx5 driver.**
The mlx5 driver was updated with changes including the following:
* Data path was refactored to bypass Verbs to improve RX and TX performance.
* Removed compilation parameters for inline send, ``MLX5_MAX_INLINE``, and
added command line parameter instead, ``txq_inline``.
* Improved TX scatter gather support:
Removed compilation parameter ``MLX5_PMD_SGE_WR_N``.
Scatter-gather elements is set to the maximum value the NIC supports.
Removed linearization logic, this decreases the memory consumption of the PMD.
* Improved jumbo frames support, by dynamically setting RX scatter gather elements
according to the MTU and mbuf size,
no need for compilation parameter ``MLX5_PMD_SGE_WR_N``
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* **Added support for virtio on IBM POWER8.**
config: enable virtio for ppc64 Now that virtio pmd is supported on ppc, enable it. Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2016-05-17 09:59:52 +00:00
The ioports are mapped in memory when using Linux UIO.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
net/virtio-user: fix inconsistent name The commit cb6696d22023 ("drivers: update registration macro usage") changes the name from virtio-user to virtio_user, because hyphen cannot be used in a C symbol name. However, this commit does not update the strings in docs and source code, which could lead to failure to start this device as per the docs. This patch updates related strings in the docs and source code. Fixes: cb6696d22023 ("drivers: update registration macro usage") Reported-by: Tiwei Bie <tiwei.bie@intel.com> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
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.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
vhost: add vhost-user client mode Add a new paramter (flags) to rte_vhost_driver_register(). DPDK vhost-user acts as client mode when RTE_VHOST_USER_CLIENT flag is set. The flags would also allow future extensions without breaking the API (again). The rest is straingfoward then: allocate a unix socket, and bind/listen for server, connect for client. This extension is for vhost-user only, therefore we simply quit and report error when any flags are given for vhost-cuse. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-06 21:26:03 +00:00
* **Added vhost-user client mode.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
vhost: add vhost-user client mode Add a new paramter (flags) to rte_vhost_driver_register(). DPDK vhost-user acts as client mode when RTE_VHOST_USER_CLIENT flag is set. The flags would also allow future extensions without breaking the API (again). The rest is straingfoward then: allocate a unix socket, and bind/listen for server, connect for client. This extension is for vhost-user only, therefore we simply quit and report error when any flags are given for vhost-cuse. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-06 21:26:03 +00:00
``rte_vhost_driver_register``.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
vhost: add vhost-user client mode Add a new paramter (flags) to rte_vhost_driver_register(). DPDK vhost-user acts as client mode when RTE_VHOST_USER_CLIENT flag is set. The flags would also allow future extensions without breaking the API (again). The rest is straingfoward then: allocate a unix socket, and bind/listen for server, connect for client. This extension is for vhost-user only, therefore we simply quit and report error when any flags are given for vhost-cuse. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-06 21:26:03 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
DPDK vhost-user will also try to reconnect by default when:
vhost: add reconnect ability Allow reconnecting on failure by default when: - DPDK app starts first and QEMU (as the server) is not started yet. Without reconnecting, DPDK app would simply fail on vhost-user registration. - QEMU restarts, say due to OS reboot. Without reconnecting, you can't re-establish the connection without restarting DPDK app. This patch make it work well for both above cases. It simply creates a new thread, and keep trying calling "connect()", until it succeeds. The reconnect could be disabled when RTE_VHOST_USER_NO_RECONNECT flag is set. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-12 23:14:19 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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).
vhost: add reconnect ability Allow reconnecting on failure by default when: - DPDK app starts first and QEMU (as the server) is not started yet. Without reconnecting, DPDK app would simply fail on vhost-user registration. - QEMU restarts, say due to OS reboot. Without reconnecting, you can't re-establish the connection without restarting DPDK app. This patch make it work well for both above cases. It simply creates a new thread, and keep trying calling "connect()", until it succeeds. The reconnect could be disabled when RTE_VHOST_USER_NO_RECONNECT flag is set. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-12 23:14:19 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
It can be turned off by setting the ``RTE_VHOST_USER_NO_RECONNECT`` flag.
vhost: add reconnect ability Allow reconnecting on failure by default when: - DPDK app starts first and QEMU (as the server) is not started yet. Without reconnecting, DPDK app would simply fail on vhost-user registration. - QEMU restarts, say due to OS reboot. Without reconnecting, you can't re-establish the connection without restarting DPDK app. This patch make it work well for both above cases. It simply creates a new thread, and keep trying calling "connect()", until it succeeds. The reconnect could be disabled when RTE_VHOST_USER_NO_RECONNECT flag is set. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-05-12 23:14:19 +00:00
net/i40e: support NSH packet type NSH packet can be recognized by Intel X710/XL710 series. This patch enables the new packet type. Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Tested-by: Yulong Pei <yulong.pei@intel.com> Acked-by: Zhe Tao <zhe.tao@intel.com>
2016-05-03 05:51:12 +00:00
* **Added NSH packet recognition in i40e.**
aesni_mb: add AES-CTR This patch provides counter mode support to AES-NI multi-buffer library. The following cipher algorithm is enabled: - RTE_CRYPTO_CIPHER_AES_CTR Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
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.
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* **Added support for AES counter mode with Intel QuickAssist devices.**
qat: add AES-CTR capability Added possibility for AES to work in counter mode Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
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.
crypto/kasumi: add driver for KASUMI library Added new SW PMD which makes use of the libsso_kasumi SW library, which provides wireless algorithms KASUMI F8 and F9 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: - RTE_CRYPTO_SYM_CIPHER_KASUMI_F8 - RTE_CRYPTO_SYM_AUTH_KASUMI_F9 Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
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.
hash: add scalable multi-writer insertion with Intel TSX This patch introduced scalable multi-writer Cuckoo Hash insertion based on a split Cuckoo Search and Move operation using Intel TSX. It can do scalable hash insertion with 22 cores with little performance loss and negligible TSX abortion rate. * Added an extra rte_hash flag definition to switch default single writer Cuckoo Hash behavior to multiwriter. - If HTM is available, it would use hardware feature for concurrency. - If HTM is not available, it would fall back to spinlock. * Created a rte_cuckoo_hash_x86.h file to hold all x86-arch related cuckoo_hash functions. And rte_cuckoo_hash.c uses compile time flag to select x86 file or other platform-specific implementations. While HTM check is still done at runtime (same idea with RTE_HASH_EXTRA_FLAGS_TRANS_MEM_SUPPORT) * Moved rte_hash private struct definitions to rte_cuckoo_hash.h, to allow rte_cuckoo_hash_x86.h or future platform dependent functions to include. * Following new functions are created for consistent names when new platform TM support are added. - rte_hash_cuckoo_move_insert_mw_tm: do insertion with bucket movement. - rte_hash_cuckoo_insert_mw_tm: do insertion without bucket movement. * One extra multi-writer test case is added. Signed-off-by: Wei Shen <wei1.shen@intel.com> Signed-off-by: Sameh Gobriel <sameh.gobriel@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
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:
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
hash: add scalable multi-writer insertion with Intel TSX This patch introduced scalable multi-writer Cuckoo Hash insertion based on a split Cuckoo Search and Move operation using Intel TSX. It can do scalable hash insertion with 22 cores with little performance loss and negligible TSX abortion rate. * Added an extra rte_hash flag definition to switch default single writer Cuckoo Hash behavior to multiwriter. - If HTM is available, it would use hardware feature for concurrency. - If HTM is not available, it would fall back to spinlock. * Created a rte_cuckoo_hash_x86.h file to hold all x86-arch related cuckoo_hash functions. And rte_cuckoo_hash.c uses compile time flag to select x86 file or other platform-specific implementations. While HTM check is still done at runtime (same idea with RTE_HASH_EXTRA_FLAGS_TRANS_MEM_SUPPORT) * Moved rte_hash private struct definitions to rte_cuckoo_hash.h, to allow rte_cuckoo_hash_x86.h or future platform dependent functions to include. * Following new functions are created for consistent names when new platform TM support are added. - rte_hash_cuckoo_move_insert_mw_tm: do insertion with bucket movement. - rte_hash_cuckoo_insert_mw_tm: do insertion without bucket movement. * One extra multi-writer test case is added. Signed-off-by: Wei Shen <wei1.shen@intel.com> Signed-off-by: Sameh Gobriel <sameh.gobriel@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2016-06-16 22:14:14 +00:00
examples/ip_pipeline: support RSS This patch enables rss (receive side scaling) per network interface through the configuration file. The user can specify following parameters in LINK section for enabling the rss feature - rss_qs, rss_proto_ipv4, rss_proto_ipv6 and ip_proto_l2. The "rss_qs" is mandatory parameter which indicates the queues to be used for rss, while rest of the parameters are optional. When optional parameters are not provided in the configuration file, default setting (ETH_RSS_IPV4 | ETH_RSS_IPV6) is assumed for "rss_hf" field of the rss_conf structure. For example, following configuration can be applied for using the rss on port 0 of the network interface; [PIPELINE0] type = MASTER core = 0 [LINK0] rss_qs = 0 1 [PIPELINE1] type = PASS-THROUGH core = 1 pktq_in = RXQ0.0 RXQ0.1 RXQ1.0 pktq_out = TXQ0.0 TXQ1.0 TXQ0.1 Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-05-30 17:14:49 +00:00
* **Improved IP Pipeline Application.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
The following features have been added to the ip_pipeline application:
examples/ip_pipeline: support RSS This patch enables rss (receive side scaling) per network interface through the configuration file. The user can specify following parameters in LINK section for enabling the rss feature - rss_qs, rss_proto_ipv4, rss_proto_ipv6 and ip_proto_l2. The "rss_qs" is mandatory parameter which indicates the queues to be used for rss, while rest of the parameters are optional. When optional parameters are not provided in the configuration file, default setting (ETH_RSS_IPV4 | ETH_RSS_IPV6) is assumed for "rss_hf" field of the rss_conf structure. For example, following configuration can be applied for using the rss on port 0 of the network interface; [PIPELINE0] type = MASTER core = 0 [LINK0] rss_qs = 0 1 [PIPELINE1] type = PASS-THROUGH core = 1 pktq_in = RXQ0.0 RXQ0.1 RXQ1.0 pktq_out = TXQ0.0 TXQ1.0 TXQ0.1 Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-05-30 17:14:49 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* Configure the MAC address in the routing pipeline and automatic route
examples/ip_pipeline: update routes when ports state change The routing pipeline registers a callback function with the nic ports and this function is invoked for updating the routing entries (corresponding to local host and directly attached network) tables whenever the nic ports change their states (up/down). Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-06-01 14:01:01 +00:00
updates with change in link state.
examples/ip_pipeline: support RSS This patch enables rss (receive side scaling) per network interface through the configuration file. The user can specify following parameters in LINK section for enabling the rss feature - rss_qs, rss_proto_ipv4, rss_proto_ipv6 and ip_proto_l2. The "rss_qs" is mandatory parameter which indicates the queues to be used for rss, while rest of the parameters are optional. When optional parameters are not provided in the configuration file, default setting (ETH_RSS_IPV4 | ETH_RSS_IPV6) is assumed for "rss_hf" field of the rss_conf structure. For example, following configuration can be applied for using the rss on port 0 of the network interface; [PIPELINE0] type = MASTER core = 0 [LINK0] rss_qs = 0 1 [PIPELINE1] type = PASS-THROUGH core = 1 pktq_in = RXQ0.0 RXQ0.1 RXQ1.0 pktq_out = TXQ0.0 TXQ1.0 TXQ0.1 Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-05-30 17:14:49 +00:00
* Enable RSS per network interface through the configuration file.
* Streamline the CLI code.
keepalive: add liveness callback Adds and documents new callbacks that allow transitions to core states other than dead to be reported to applications. Signed-off-by: Remy Horton <remy.horton@intel.com>
2016-06-15 15:25:50 +00:00
* **Added keepalive enhancements.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
Added support for reporting of core states other than dead to
keepalive: add liveness callback Adds and documents new callbacks that allow transitions to core states other than dead to be reported to applications. Signed-off-by: Remy Horton <remy.horton@intel.com>
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.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
net/i40e: add floating VEB option The standard Virtual Ethernet Bridge(VEB) definition in 1Qbg is a bridge which has an uplink port to the outside world (maybe another bridge), but a "floating" VEB is a special VEB without an uplink port to the outside. Instead, traffic can be sent from one VF to another using the floating VEB - even when the physical link on the NIC port is down. This patch adds floating VEB options in the devargs for i40e driver. Using these parameters, applications can decide whether to use legacy VEB/VEPA or a floating VEB. To enable this feature, the user should pass a devargs parameter to the EAL, for example "-w 84:00.0,enable_floating_veb=1", to control whether the PMD will to use the floating VEB feature or not. Once the floating VEB feature is enabled, all the VFs created by this PF device are connected to the floating VEB. NOTE: The floating VEB functionality requires a NIC firmware version of 5.0 or greater. Signed-off-by: Zhe Tao <zhe.tao@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add VF live migration howto with bonded virtio This patch describes the procedure to be be followed to perform Live Migration of a VM with Virtio and VF PMD's using the bonding PMD. It includes sample host and VM scripts used in the procedure, and a sample switch configuration. Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
net/i40e: add floating VEB option The standard Virtual Ethernet Bridge(VEB) definition in 1Qbg is a bridge which has an uplink port to the outside world (maybe another bridge), but a "floating" VEB is a special VEB without an uplink port to the outside. Instead, traffic can be sent from one VF to another using the floating VEB - even when the physical link on the NIC port is down. This patch adds floating VEB options in the devargs for i40e driver. Using these parameters, applications can decide whether to use legacy VEB/VEPA or a floating VEB. To enable this feature, the user should pass a devargs parameter to the EAL, for example "-w 84:00.0,enable_floating_veb=1", to control whether the PMD will to use the floating VEB feature or not. Once the floating VEB feature is enabled, all the VFs created by this PF device are connected to the floating VEB. NOTE: The floating VEB functionality requires a NIC firmware version of 5.0 or greater. Signed-off-by: Zhe Tao <zhe.tao@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-06-29 13:06:03 +00:00
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Resolved Issues
---------------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain bug fixes added to the relevant sections. Sample format:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
* **code/section Fixed issue in the past tense with a full stop.**
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
EAL
~~~
igb_uio: fix possible mmap failure with Linux 4.5 mmap the iomem range of the PCI device fails for kernels that enabled CONFIG_IO_STRICT_DEVMEM option: EAL: pci_map_resource(): cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0): Invalid argument (0xffffffffffffffff) CONFIG_IO_STRICT_DEVMEM is introduced in Linux v4.5 and not enabled by default: Linux commit: 90a545e restrict /dev/mem to idle io memory ranges As a workaround igb_uio can stop reserving PCI memory resources, from kernel point of view iomem region looks like idle and mmap works again. This matches uio_pci_generic usage. With this update device iomem range is not protected against any other kernel drivers or userspace access. But this shouldn't be a problem for dpdk usage module since purpose of the igb_uio module is to provide userspace access. Fixes: af75078fece3 ("first public release") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-07-05 15:00:52 +00:00
* **igb_uio: Fixed possible mmap failure for Linux >= 4.5.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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::
igb_uio: fix possible mmap failure with Linux 4.5 mmap the iomem range of the PCI device fails for kernels that enabled CONFIG_IO_STRICT_DEVMEM option: EAL: pci_map_resource(): cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0): Invalid argument (0xffffffffffffffff) CONFIG_IO_STRICT_DEVMEM is introduced in Linux v4.5 and not enabled by default: Linux commit: 90a545e restrict /dev/mem to idle io memory ranges As a workaround igb_uio can stop reserving PCI memory resources, from kernel point of view iomem region looks like idle and mmap works again. This matches uio_pci_generic usage. With this update device iomem range is not protected against any other kernel drivers or userspace access. But this shouldn't be a problem for dpdk usage module since purpose of the igb_uio module is to provide userspace access. Fixes: af75078fece3 ("first public release") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-07-05 15:00:52 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
EAL: pci_map_resource():
igb_uio: fix possible mmap failure with Linux 4.5 mmap the iomem range of the PCI device fails for kernels that enabled CONFIG_IO_STRICT_DEVMEM option: EAL: pci_map_resource(): cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0): Invalid argument (0xffffffffffffffff) CONFIG_IO_STRICT_DEVMEM is introduced in Linux v4.5 and not enabled by default: Linux commit: 90a545e restrict /dev/mem to idle io memory ranges As a workaround igb_uio can stop reserving PCI memory resources, from kernel point of view iomem region looks like idle and mmap works again. This matches uio_pci_generic usage. With this update device iomem range is not protected against any other kernel drivers or userspace access. But this shouldn't be a problem for dpdk usage module since purpose of the igb_uio module is to provide userspace access. Fixes: af75078fece3 ("first public release") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-07-05 15:00:52 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0):
Invalid argument (0xffffffffffffffff)
igb_uio: fix possible mmap failure with Linux 4.5 mmap the iomem range of the PCI device fails for kernels that enabled CONFIG_IO_STRICT_DEVMEM option: EAL: pci_map_resource(): cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0): Invalid argument (0xffffffffffffffff) CONFIG_IO_STRICT_DEVMEM is introduced in Linux v4.5 and not enabled by default: Linux commit: 90a545e restrict /dev/mem to idle io memory ranges As a workaround igb_uio can stop reserving PCI memory resources, from kernel point of view iomem region looks like idle and mmap works again. This matches uio_pci_generic usage. With this update device iomem range is not protected against any other kernel drivers or userspace access. But this shouldn't be a problem for dpdk usage module since purpose of the igb_uio module is to provide userspace access. Fixes: af75078fece3 ("first public release") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-07-05 15:00:52 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
igb_uio: fix possible mmap failure with Linux 4.5 mmap the iomem range of the PCI device fails for kernels that enabled CONFIG_IO_STRICT_DEVMEM option: EAL: pci_map_resource(): cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0): Invalid argument (0xffffffffffffffff) CONFIG_IO_STRICT_DEVMEM is introduced in Linux v4.5 and not enabled by default: Linux commit: 90a545e restrict /dev/mem to idle io memory ranges As a workaround igb_uio can stop reserving PCI memory resources, from kernel point of view iomem region looks like idle and mmap works again. This matches uio_pci_generic usage. With this update device iomem range is not protected against any other kernel drivers or userspace access. But this shouldn't be a problem for dpdk usage module since purpose of the igb_uio module is to provide userspace access. Fixes: af75078fece3 ("first public release") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-07-05 15:00:52 +00:00
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Drivers
~~~~~~~
i40e: fix 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, what is not expected behaviour. This patch fixes it by changing hardware configuration to leave the inner packet alone. Fixes: 4861cde46116 ("i40e: new poll mode driver") Fixes: a778a1fa2e4e ("i40e: set up and initialize flow director") Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
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.
net/i40e: fix single VLAN tag to be outer VLAN tag In current i40e codebase, if single VLAN header is added in a packet, it's treated as inner VLAN. Generally, a single VLAN header is treated as the outer VLAN header, so update the driver behaviour appropriately. Fixes: 19b16e2f6442 ("ethdev: add vlan type when setting ether type") Signed-off-by: Beilei Xing <beilei.xing@intel.com>
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.
doc: update release notes and guide for enic Signed-off-by: John Daley <johndale@cisco.com>
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.**
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Libraries
~~~~~~~~~
mbuf: decrease reference counter when detaching The rte_pktmbuf_detach() function should decrease refcnt on a direct buffer as stated in doc/guides/prog_guide/mbuf_lib.rst: "whenever the indirect buffer is detached, the reference counter on the direct buffer is decremented." Signed-off-by: Hiroyuki Mikita <h.mikita89@gmail.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2016-05-18 14:41:03 +00:00
* **mbuf: Fixed refcnt update when detaching.**
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
mbuf: decrease reference counter when detaching The rte_pktmbuf_detach() function should decrease refcnt on a direct buffer as stated in doc/guides/prog_guide/mbuf_lib.rst: "whenever the indirect buffer is detached, the reference counter on the direct buffer is decremented." Signed-off-by: Hiroyuki Mikita <h.mikita89@gmail.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2016-05-18 14:41:03 +00:00
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Examples
~~~~~~~~
Other
~~~~~
Known Issues
------------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain new known issues in this release. Sample format:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
* **Add title in present tense with full stop.**
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
API Changes
-----------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain API changes. Sample format:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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``
ethdev: remove deprecated statistics Some statistics were deprecated since release 2.1 (49f386542af4). The last deprecated counter to be used was imcasts. The VF loopback statistics are also removed as they are used only in igb and duplicated in extended statistics. The new counters should be added to extended statistics. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Remy Horton <remy.horton@intel.com>
2016-04-15 09:01:51 +00:00
ethdev: remove name from extended statistic fetch The current extended ethernet statistics fetching involve doing several string operations, which causes performance issues if there are lots of statistics and/or network interfaces. This patch changes the test-pmd and proc_info applications to use the new xstats API, and removes deprecated code associated with the old API. Signed-off-by: Remy Horton <remy.horton@intel.com>
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``.
ethdev: get queues numbers The new fields nb_rx_queues and nb_tx_queues are added to the rte_eth_dev_info structure. Changes to API rte_eth_dev_info_get() are done to update these new fields to the rte_eth_dev_info object. Release notes is updated with the changes. The librte_pdump library needs to register Rx and Tx callbacks for all the nb_rx_queues and nb_tx_queues, when application wants to capture the packets on all the software configured number of Rx and Tx queues of the device. So far there is no support to get nb_rx_queues and nb_tx_queues information from the ethdev library. Hence these changes are introduced. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
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``.
vhost: export queue free entries The new API rte_vhost_avail_entries() is actually a rename of rte_vring_available_entries(), with the "vring" to "vhost" name change to keep the consistency of other vhost exported APIs. This change could let us avoid the dependency of "virtio_net" struct, to prepare for the ABI refactoring. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Acked-by: Rich Lane <rich.lane@bigswitch.com>
2016-05-10 22:46:24 +00:00
* The vhost function ``rte_vring_available_entries`` is renamed to
``rte_vhost_avail_entries``.
vhost: export device id as the interface to applications With all the previous prepare works, we are just one step away from the final ABI refactoring. That is, to change current API to let them stick to vid instead of the old virtio_net dev. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Acked-by: Rich Lane <rich.lane@bigswitch.com>
2016-06-13 09:55:49 +00:00
* All existing vhost APIs and callbacks with ``virtio_net`` struct pointer
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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``.
vhost: export device id as the interface to applications With all the previous prepare works, we are just one step away from the final ABI refactoring. That is, to change current API to let them stick to vid instead of the old virtio_net dev. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Acked-by: Rich Lane <rich.lane@bigswitch.com>
2016-06-13 09:55:49 +00:00
vhost: remove concurrent enqueue All other DPDK PMDs doesn't support concurrent receiving or sending packets to the same queue. The upper application should deal with this, normally through queue and core bindings. Due to historical reason, vhost internally supports concurrent lockless enqueuing packets to the same virtio queue through costly cmpset operation. This patch removes this internal lockless implementation and should improve performance a bit. Luckily DPDK OVS doesn't rely on this behavior. Signed-off-by: Huawei Xie <huawei.xie@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-06-13 11:52:12 +00:00
* The function ``rte_vhost_enqueue_burst`` no longer supports concurrent enqueuing
packets to the same queue.
net/i40e: support MTU configuration This patch enables configuring MTU for i40e. Since changing MTU needs to reconfigure queue, the port must be stopped before configuring MTU. Signed-off-by: Beilei Xing <beilei.xing@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
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.
unify tools naming The following tools may be installed system-wide. It may be cleaner and more convenient to find them with the same dpdk- prefix (especially for autocompletion). Moreover, the script dpdk_nic_bind.py deserves a new name because it is not restricted to NICs and can be used for e.g. crypto. These files are renamed: pmdinfogen -> dpdk-pmdinfogen pmdinfo.py -> dpdk-pmdinfo.py dpdk_pdump -> dpdk-pdump dpdk_proc_info -> dpdk-procinfo dpdk_nic_bind.py -> dpdk-devbind.py setup.sh -> dpdk-setup.sh The tools pmdinfogen, pmdinfo.py and dpdk_pdump are new in 16.07. The scripts dpdk_nic_bind.py and setup.sh may have been used with previous releases by end users. That's why a symbolic link still provide the old name in the installed tools directory. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-07-20 13:38:54 +00:00
* The script ``dpdk_nic_bind.py`` is renamed to ``dpdk-devbind.py``.
And the script ``setup.sh`` is renamed to ``dpdk-setup.sh``.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
ABI Changes
-----------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
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.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
* The ``rte_port_source_params`` structure has new fields to support PCAP files.
port: bump ABI for pcap file support Support of PCAP file has been added to rte_port in release 16.04 as NEXT_ABI. It is in the standard ABI of the release 16.07. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-04-14 17:15:13 +00:00
It was already in release 16.04 with ``RTE_NEXT_ABI`` flag.
ethdev: get queues numbers The new fields nb_rx_queues and nb_tx_queues are added to the rte_eth_dev_info structure. Changes to API rte_eth_dev_info_get() are done to update these new fields to the rte_eth_dev_info object. Release notes is updated with the changes. The librte_pdump library needs to register Rx and Tx callbacks for all the nb_rx_queues and nb_tx_queues, when application wants to capture the packets on all the software configured number of Rx and Tx queues of the device. So far there is no support to get nb_rx_queues and nb_tx_queues information from the ethdev library. Hence these changes are introduced. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:20 +00:00
* The ``rte_eth_dev_info`` structure has new fields ``nb_rx_queues`` and ``nb_tx_queues``
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-07-19 13:16:35 +00:00
to support the number of queues configured by software.
ethdev: get queues numbers The new fields nb_rx_queues and nb_tx_queues are added to the rte_eth_dev_info structure. Changes to API rte_eth_dev_info_get() are done to update these new fields to the rte_eth_dev_info object. Release notes is updated with the changes. The librte_pdump library needs to register Rx and Tx callbacks for all the nb_rx_queues and nb_tx_queues, when application wants to capture the packets on all the software configured number of Rx and Tx queues of the device. So far there is no support to get nb_rx_queues and nb_tx_queues information from the ethdev library. Hence these changes are introduced. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:20 +00:00
doc: fix release notes for 16.07 Fix grammar, spelling and formatting of DPDK 16.07 release notes. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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.
vhost: export device id as the interface to applications With all the previous prepare works, we are just one step away from the final ABI refactoring. That is, to change current API to let them stick to vid instead of the old virtio_net dev. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Acked-by: Rich Lane <rich.lane@bigswitch.com>
2016-06-13 09:55:49 +00:00
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Shared Library Versions
-----------------------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. Update any library version updated in this release and prepend with a ``+`` sign.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
The libraries prepended with a plus sign were incremented in this version.
.. code-block:: diff
ethdev: remove deprecated statistics Some statistics were deprecated since release 2.1 (49f386542af4). The last deprecated counter to be used was imcasts. The VF loopback statistics are also removed as they are used only in igb and duplicated in extended statistics. The new counters should be added to extended statistics. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Remy Horton <remy.horton@intel.com>
2016-04-15 09:01:51 +00:00
+ libethdev.so.4
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
librte_acl.so.2
librte_cfgfile.so.2
librte_cmdline.so.2
doc: add cryptodev shared library version to release notes Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2016-07-20 12:31:12 +00:00
librte_cryptodev.so.1
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
mempool: reduce structure size if no cache needed The rte_mempool structure is changed, which will cause an ABI change for this structure. Providing backward compat is not reasonable here as this structure is used in multiple defines/inlines. Allow mempool cache support to be dynamic depending on if the mempool being created needs cache support. Saves about 1.5M of memory used by the rte_mempool structure. Allocating small mempools which do not require cache can consume larges amounts of memory if you have a number of these mempools. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2016-04-14 09:42:36 +00:00
+ librte_mempool.so.2
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
librte_meter.so.1
doc: add pdump shared library version to release notes Added missing librte_pdump shared library version to release notes. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-07-06 15:57:40 +00:00
librte_pdump.so.1
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
librte_pipeline.so.3
librte_pmd_bond.so.1
librte_pmd_ring.so.2
port: bump ABI for pcap file support Support of PCAP file has been added to rte_port in release 16.04 as NEXT_ABI. It is in the standard ABI of the release 16.07. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-04-14 17:15:13 +00:00
+ librte_port.so.3
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
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
vhost: export device id as the interface to applications With all the previous prepare works, we are just one step away from the final ABI refactoring. That is, to change current API to let them stick to vid instead of the old virtio_net dev. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Acked-by: Rich Lane <rich.lane@bigswitch.com>
2016-06-13 09:55:49 +00:00
+ librte_vhost.so.3
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Tested Platforms
----------------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain a list of platforms that were tested with this
release.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
The format is:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
#. Platform name.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
- Platform details.
- Platform details.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
Tested NICs
-----------
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
.. This section should contain a list of NICs that were tested with this release.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
The format is:
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
#. NIC name.
doc: add template release notes for 16.07 Added template release notes for DPDK 16.07 with inline explanations of the various sections. Signed-off-by: John McNamara <john.mcnamara@intel.com>
2016-04-12 12:55:10 +00:00
doc: move release notes instructions as comments We don't want to have this instructions in the generated docs, so use comments. It's also less confusing for people adding entries in the documentation. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-05-13 13:27:59 +00:00
- NIC details.
- NIC details.
Reference in New Issue Copy Permalink