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

606 lines
23 KiB
ReStructuredText
Raw Normal View History

version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
.. SPDX-License-Identifier: BSD-3-Clause
Copyright 2018 The DPDK contributors
DPDK Release 18.11
==================
.. **Read this first.**
The text in the sections below explains how to update the release notes.
Use proper spelling, capitalization and punctuation in all sections.
Variable and config names should be quoted as fixed width text:
``LIKE_THIS``.
Build the docs and view the output file to ensure the changes are correct::
make doc-guides-html
xdg-open build/doc/html/guides/rel_notes/release_18_11.html
New Features
------------
.. This section should contain new features added in this release.
Sample format:
* **Add a title in the past tense with a full stop.**
Add a short 1-2 sentence description in the past tense.
The description should be enough to allow someone scanning
the release notes to understand the new feature.
If the feature adds a lot of sub-features you can use a bullet list
like this:
* Added feature foo to do something.
* Enhanced feature bar to do something else.
Refer to the previous release notes for examples.
Suggested order in release notes items:
* Core libs (EAL, mempool, ring, mbuf, buses)
* Device abstraction libs and PMDs
- ethdev (lib, PMDs)
- cryptodev (lib, PMDs)
- eventdev (lib, PMDs)
- etc
* Other libs
* Apps, Examples, Tools (if significative)
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
doc: add external memory feature Document the addition of external memory support to DPDK. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-02 13:34:58 +00:00
* **Added support for using externally allocated memory in DPDK.**
DPDK has gained support for creating new ``rte_malloc`` heaps referencing
memory that was created outside of DPDK's own page allocator, and using that
memory natively with any other DPDK library or data structure.
mem: add function for checking memseg IOVA A device can suffer addressing limitations. This function checks memsegs have iovas within the supported range based on dma mask. PMDs should use this function during initialization if device suffers addressing limitations, returning an error if this function returns memsegs out of range. Another usage is for emulated IOMMU hardware with addressing limitations. It is necessary to save the most restricted dma mask for checking out memory allocated dynamically after initialization. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-05 12:45:22 +00:00
* **Added check for ensuring allocated memory addressable by devices.**
Some devices can have addressing limitations so a new function,
mem: rename DMA mask check with proper prefix Current name rte_eal_check_dma_mask does not follow the naming used in the rest of the file. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-11-01 19:53:25 +00:00
``rte_mem_check_dma_mask``, has been added for checking allocated memory is
mem: add function for checking memseg IOVA A device can suffer addressing limitations. This function checks memsegs have iovas within the supported range based on dma mask. PMDs should use this function during initialization if device suffers addressing limitations, returning an error if this function returns memsegs out of range. Another usage is for emulated IOMMU hardware with addressing limitations. It is necessary to save the most restricted dma mask for checking out memory allocated dynamically after initialization. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-05 12:45:22 +00:00
not out of the device range. Because now memory can be dynamically allocated
after initialization, a dma mask is kept and any new allocated memory will be
checked out against that dma mask and rejected if out of range. If more than
one device has addressing limitations, the dma mask is the more restricted one.
ring/c11: move atomic load of head above the loop In __rte_ring_move_prod_head, move the __atomic_load_n up and out of the do {} while loop as upon failure the old_head will be updated, another load is costly and not necessary. This helps a little on the latency,about 1~5%. Test result with the patch(two cores): SP/SC bulk enq/dequeue (size: 8): 5.64 MP/MC bulk enq/dequeue (size: 8): 9.58 SP/SC bulk enq/dequeue (size: 32): 1.98 MP/MC bulk enq/dequeue (size: 32): 2.30 Fixes: 39368ebfc606 ("ring: introduce C11 memory model barrier option") Cc: stable@dpdk.org Signed-off-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Reviewed-by: Jia He <justin.he@arm.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Tested-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2018-11-02 11:21:28 +00:00
* **Updated the C11 memory model version of ring library.**
The latency is decreased for architectures using the C11 memory model
version of the ring library.
On Cavium ThunderX2 platform, the changes decreased latency by 27~29%
and 3~15% for MPMC and SPSC cases respectively (with 2 lcores). The
real improvements may vary with the number of contending lcores and
the size of ring.
eal: add failure handling for hot-unplug The mechanism can initially register the sigbus handler after the device event monitor is enabled. When a sigbus event is captured, it will check the failure address and accordingly handle the memory failure of the corresponding device by invoke the hot-unplug handler. It could prevent the application from crashing when a device is hot-unplugged. By this patch, users could call below new added APIs to enable/disable the device hotplug handle mechanism. Note that it just implement the hot-unplug handler in these functions, the other handler of hotplug, such as handler for hotplug binding, could be add in the future if need: - rte_dev_hotplug_handle_enable - rte_dev_hotplug_handle_disable Signed-off-by: Jeff Guo <jia.guo@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2018-10-15 11:27:26 +00:00
* **Added hot-unplug handle mechanism.**
``rte_dev_hotplug_handle_enable`` and ``rte_dev_hotplug_handle_disable`` are
for enabling or disabling hotplug handle mechanism.
eal: enable hotplug on multi-process We are going to introduce the solution to handle hotplug in multi-process, it includes the below scenario: 1. Attach a device from the primary 2. Detach a device from the primary 3. Attach a device from a secondary 4. Detach a device from a secondary In the primary-secondary process model, we assume devices are shared by default. that means attaches or detaches a device on any process will broadcast to all other processes through mp channel then device information will be synchronized on all processes. Any failure during attaching/detaching process will cause inconsistent status between processes, so proper rollback action should be considered. This patch covers the implementation of case 1,2. Case 3,4 will be implemented on a separate patch. IPC scenario for Case 1, 2: attach a device a) primary attach the new device if failed goto h). b) primary send attach sync request to all secondary. c) secondary receive request and attach the device and send a reply. d) primary check the reply if all success goes to i). e) primary send attach rollback sync request to all secondary. f) secondary receive the request and detach the device and send a reply. g) primary receive the reply and detach device as rollback action. h) attach fail i) attach success detach a device a) primary send detach sync request to all secondary b) secondary detach the device and send reply c) primary check the reply if all success goes to f). d) primary send detach rollback sync request to all secondary. e) secondary receive the request and attach back device. goto g) f) primary detach the device if success goto g), else goto d) g) detach fail. h) detach success. Signed-off-by: Qi Zhang <qi.z.zhang@intel.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-16 00:16:28 +00:00
* **Support device multi-process hotplug.**
Hotplug and hot-unplug for devices will now be supported in multiprocessing
scenario. Any ethdev devices created in the primary process will be regarded
as shared and will be available for all DPDK processes. Synchronization
between processes will be done using DPDK IPC.
ethdev: add flow API actions to modify IP addresses Add actions: - SET_IPV4_SRC - set a new IPv4 source address. - SET_IPV4_DST - set a new IPv4 destination address. - SET_IPV6_SRC - set a new IPv6 source address. - SET_IPV6_DST - set a new IPv6 destination address. Original work by Shagun Agrawal Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Acked-by: Xiaoyu Min <jackmin@mellanox.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-09 08:44:36 +00:00
* **Added new Flow API actions to rewrite fields in packet headers.**
Added new Flow API actions to:
* Modify source and destination IP addresses in the outermost IPv4/IPv6
headers.
ethdev: add flow API actions to modify TCP/UDP port numbers Add actions: - SET_TP_SRC - set a new TCP/UDP source port number. - SET_TP_DST - set a new TCP/UDP destination port number. Original work by Shagun Agrawal Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Acked-by: Xiaoyu Min <jackmin@mellanox.com> Acked-by: Ori Kam <orika@mellanox.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-09 08:44:37 +00:00
* Modify source and destination port numbers in the outermost TCP/UDP
headers.
ethdev: add flow API actions to modify IP addresses Add actions: - SET_IPV4_SRC - set a new IPv4 source address. - SET_IPV4_DST - set a new IPv4 destination address. - SET_IPV6_SRC - set a new IPv6 source address. - SET_IPV6_DST - set a new IPv6 destination address. Original work by Shagun Agrawal Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Acked-by: Xiaoyu Min <jackmin@mellanox.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-09 08:44:36 +00:00
ethdev: add flow action to swap MAC addresses This action is useful for offloading loopback mode, where the hardware will swap source and destination MAC addresses in the outermost Ethernet header before looping back the packet. This action can be used in conjunction with other rewrite actions to achieve MAC layer transparent NAT where the MAC addresses are swapped before either the source or destination MAC address is rewritten and NAT is performed. Must be used with a valid RTE_FLOW_ITEM_TYPE_ETH flow pattern item. Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error should be returned by the PMDs. Original work by Shagun Agrawal Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-06 15:45:34 +00:00
* **Added new Flow API action to swap MAC addresses in Ethernet header.**
Added new Flow API action to swap the source and destination MAC
addresses in the outermost Ethernet header.
net/cxgbe: add flow operations to offload VLAN actions Add flow API operations to offload vlan push, pop, and rewrite actions. For vlan push or rewrite actions, allocate and program an entry from L2T table. Use the L2T index to program vlan actions for LETCAM (maskfull) and HASH (maskless) filters. Signed-off-by: Shagun Agrawal <shaguna@chelsio.com> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
2018-08-27 12:52:30 +00:00
* **Add support to offload more flow match and actions for CXGBE PMD**
Flow API support has been enhanced for CXGBE Poll Mode Driver to offload:
net/cxgbe: add flow ops to match based on dest MAC Add flow operations to match packets based on destination MAC address. Allocate and program hardware MPS table with the destination MAC address to be matched against. The returned MPS index is then used while offloading flows to LETCAM (maskfull) and HASH (maskless) filter regions. Also update existing mac_addr_set() to use the new MPS table API. Signed-off-by: Shagun Agrawal <shaguna@chelsio.com> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
2018-08-27 12:52:32 +00:00
* Match items: destination MAC address.
net/cxgbe: add flow actions to modify IP and TCP/UDP port Query firmware for the new filter work request to offload flows with actions to modify IP and TCP/UDP port addresses. When available, translate IP and TCP/UDP port address modify actions to internal hardware specification and offload the flow to hardware. Original work by Shagun Agrawal Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
2018-10-09 08:44:38 +00:00
* Action items: push/pop/rewrite vlan header,
rewrite IP addresses in outermost IPv4/IPv6 header,
net/cxgbe: add action to swap MAC addresses Implement RTE_FLOW_ACTION_TYPE_MAC_SWAP to offload flows with action to swap the source and destination MAC addresses in the outermost Ethernet header. Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
2018-10-15 14:05:13 +00:00
rewrite port numbers in outermost TCP/UDP header,
swap MAC addresses in outermost Ethernet header.
net/cxgbe: add flow operations to offload VLAN actions Add flow API operations to offload vlan push, pop, and rewrite actions. For vlan push or rewrite actions, allocate and program an entry from L2T table. Use the L2T index to program vlan actions for LETCAM (maskfull) and HASH (maskless) filters. Signed-off-by: Shagun Agrawal <shaguna@chelsio.com> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
2018-08-27 12:52:30 +00:00
net/i40e: add option to use latest vector path For IA, the AVX2 vector path is only recommended to be used on later platforms (identified by AVX512 support, like SKL etc.) This is because performance benchmark shows downgrade when running AVX2 vector path on early platform (BDW/HSW) in some cases. But we still observe perf gain with some real work loading. So this patch introduced the new devarg use-latest-supported-vec to force the driver always selecting the latest supported vec path. Then apps are able to take AVX2 path on early platforms. And this logic can be re-used if we will have AVX512 vec path in future. This patch only affects IA platforms. The selected vec path would be like the following: Without devarg/devarg = 0: Machine vPMD AVX512F AVX2 AVX2 SSE4.2 SSE4.2 SSE4.2 <SSE4.2 Not Supported With devarg = 1 Machine vPMD AVX512F AVX2 AVX2 AVX2 SSE4.2 SSE4.2 <SSE4.2 Not Supported Other platforms can also apply the same logic if necessary in future. Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
2018-09-18 02:22:40 +00:00
* **Added a devarg to use the latest supported vector path in i40e.**
A new devarg ``use-latest-supported-vec`` was introduced to allow users to
choose the latest vector path that the platform supported. For example, users
can use AVX2 vector path on BDW/HSW to get better performance.
net/netvsc: support integrated VF Integrate accelerated networking support into netvsc PMD. This allows netvsc to manage VF without using failsafe or vdev_netvsc. For the exception vswitch path some tests like transmit get a 22% increase in packets/sec. For the VF path, the code is slightly shorter but has no real change in performance. Pro: * using netvsc is more like other DPDK NIC's * the exception packet uses less CPU * much smaller code size * no locking required on VF transmit/receive path * no legacy Linux network device to get mangled by userspace * much simpler (1K vs 9K) LOC * unified extended statistics Con: * using netvsc has more complex startup model * no bifurcated driver support * no flow support (since host does not have flow API). * no tunnel offload support * no receive interrupt support Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-08-30 22:35:12 +00:00
* **Added support for SR-IOV in netvsc PMD.**
The ``netvsc`` poll mode driver now supports the Accelerated Networking
SR-IOV option in Hyper-V and Azure. This is an alternative to the previous
vdev_netvsc, tap, and failsafe drivers combination.
net/mvneta: add PMD skeleton Add neta pmd driver skeleton providing base for the further development. Signed-off-by: Natalie Samsonov <nsamsono@marvell.com> Signed-off-by: Yelena Krivosheev <yelena@marvell.com> Signed-off-by: Dmitri Epshtein <dima@marvell.com> Signed-off-by: Zyta Szpak <zr@semihalf.com> Signed-off-by: Andrzej Ostruszka <amo@semihalf.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 07:22:09 +00:00
* **Added a new net driver for Marvell Armada 3k device.**
Added the new ``mvneta`` net driver for Marvell Armada 3k device. See the
:doc:`../nics/mvneta` NIC guide for more details on this new driver.
doc: add guide for ENETC PMD Add enetc usage document to compile and run the DPDK application on enetc supported platform. This document introduces the enetc driver, supported platforms and supported features. Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 13:36:08 +00:00
* **Added NXP ENETC PMD.**
Added the new enetc driver for NXP enetc platform. See the
"ENETC Poll Mode Driver" document for more details on this new driver.
net/atlantic: add release notes Release notes for Aquantia atlantic driver. Signed-off-by: Igor Russkikh <igor.russkikh@aquantia.com> Signed-off-by: Pavel Belous <pavel.belous@aquantia.com>
2018-10-12 11:09:55 +00:00
* **Added Ethernet poll mode driver for Aquantia aQtion family of 10G devices.**
Added the new ``atlantic`` ethernet poll mode driver for Aquantia XGBE devices.
See the :doc:`../nics/atlantic` nic driver guide for more details on this
driver.
doc: add mlx5 release notes Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
2018-11-19 12:46:44 +00:00
* **Updated mlx5 driver.**
Updated the mlx5 driver including the following changes:
* Improved security of PMD to prevent the NIC from getting stuck when
application misbehaves.
* reworked flow engine to supported e-switch flow rules (transfer attribute).
* Supported header re-write(L2-L4), VXLAN encap/decap, count ,match
on TCP flags and multiple flow groups with e-switch flow rules.
* Supported match on medatada, VXLAN and MPLS encap/decap with flow rules.
* Supported RTE_ETH_DEV_CLOSE_REMOVE flag to provide better support for
representors.
* Supported meson build.
* Fixed build issue with PPC.
* Supported BlueField VF.
* Supported externally allocated static memory for DMA.
net/sfc: support Rx scatter in EF10 Rx datapath Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Ivan Malov <ivan.malov@oktetlabs.ru>
2018-10-03 09:03:55 +00:00
* **Updated Solarflare network PMD.**
Updated the sfc_efx driver including the following changes:
* Added support for Rx scatter in EF10 datapath implementation.
net/sfc: support Rx descriptor status on EF10 datapath Signed-off-by: Igor Romanov <igor.romanov@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Ivan Malov <ivan.malov@oktetlabs.ru>
2018-10-03 09:03:56 +00:00
* Added support for Rx descriptor status API in EF10 datapath implementation.
net/sfc: support TSO in EF10 Tx datapath Implementation includes following limitations: 1) Packet's header length must be less than 256 (SFC_TSOH_STD_LEN); 2) Offset of the TCP header must be less than 208 (EF10_TCP_HEADER_OFFSET_LIMIT); 3) Number of Tx descriptors must be not less than number of descriptors needed for TSO settings plus header plus one data segment. If above conditions are not met, the packet is dropped. If the maximum descriptor space is insufficient to hold entire TSO packet, only a part of the packet is sent. Signed-off-by: Igor Romanov <igor.romanov@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-05 14:47:02 +00:00
* Added support for TSO in EF10 datapath implementation.
net/sfc: support Tx descriptor status on EF10 datapath The implementation is shared by ef10 and ef10_simple datapaths. Signed-off-by: Igor Romanov <igor.romanov@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-05 14:47:03 +00:00
* Added support for Tx descriptor status API in EF10 (ef10 and ef10_simple)
datapaths implementation.
net/sfc: support Rx scatter in EF10 Rx datapath Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Ivan Malov <ivan.malov@oktetlabs.ru>
2018-10-03 09:03:55 +00:00
doc: update release notes for enic Fixes: 8a6ff33d6d36 ("net/enic: add AVX2 based vectorized Rx handler") Fixes: 86df6c4e2fce ("net/enic: support flow counter action") Fixes: 70401fd7784d ("net/enic: add VLAN and csum offloads to simple Tx handler") Fixes: c0aae00d7da0 ("net/enic: enable IOVA mode") Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com> Reviewed-by: John Daley <johndale@cisco.com>
2018-10-20 08:32:49 +00:00
* **Updated the enic driver.**
* Added AVX2-based vectorized Rx handler.
* Added VLAN and checksum offloads to the simple Tx handler.
* Added the count flow action.
* Enabled the virtual address IOVA mode.
net/failsafe: add Rx queue start and stop functions Support Rx queue deferred start. Signed-off-by: Ian Dolzhansky <ian.dolzhansky@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2018-09-20 13:55:51 +00:00
* **Updated failsafe driver.**
Updated the failsafe driver including the following changes:
net/failsafe: add Tx queue start and stop functions Support Tx queue deferred start. Signed-off-by: Ian Dolzhansky <ian.dolzhansky@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2018-09-20 13:55:52 +00:00
* Support for Rx and Tx queues start and stop.
* Support for Rx and Tx queues deferred start.
net/failsafe: support runtime Tx queues setup Signed-off-by: Ian Dolzhansky <ian.dolzhansky@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-08-31 16:09:38 +00:00
* Support for runtime Rx and Tx queues setup.
net/failsafe: support multicast address list set Signed-off-by: Evgeny Im <evgeny.im@oktetlabs.com> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2018-09-21 15:36:22 +00:00
* Support multicast MAC address set.
net/failsafe: add Rx queue start and stop functions Support Rx queue deferred start. Signed-off-by: Ian Dolzhansky <ian.dolzhansky@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2018-09-20 13:55:51 +00:00
net/pcap: support physical interface MAC address At the moment, PCAP interfaces use dummy MAC by default. This change adds support for selecting PCAP physical interface MAC with phy_mac=1 devarg. This allows to setup packet flows using the physical interface MAC. Signed-off-by: Juhamatti Kuusisaari <juhamatti.kuusisaari@coriant.com> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-06 00:49:59 +00:00
* **Added a devarg to use PCAP interface physical MAC address.**
A new devarg ``phy_mac`` was introduced to allow users to use physical
MAC address of the selected PCAP interface.
net/tap: access primary process queues from secondary In the case the device is created by the primary process, the secondary must request some file descriptors to attach the queues. The file descriptors are shared via IPC Unix socket. Thanks to the IPC synchronization, the secondary process is now able to do Rx/Tx on a TAP created by the primary process. Signed-off-by: Raslan Darawsheh <rasland@mellanox.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-18 10:17:29 +00:00
* **Added TAP Rx/Tx queues sharing with a secondary process.**
A secondary process can attach a TAP device created in the primary process,
probe the queues, and process Rx/Tx in a secondary process.
doc: update softnic guide for flow and QoS support Update document with flow and qos api support in softnic PMD. Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Reviewed-by: Marko Kovacevic <marko.kovacevic@intel.com>
2018-10-18 14:54:13 +00:00
* **Added classification and metering support to SoftNIC PMD.**
Added support for flow classification (rte_flow API), and metering and
policing (rte_mtr API) to the SoftNIC PMD.
net/softnic: add crypto commands This patch updates the CLI parsing of softnic with extra symmetric cryptodev, port, session, and action support. Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-10-24 12:49:04 +00:00
* **Added Crypto support to Softnic PMD.**
The Softnic is now capable of processing symmetric crypto workloads such
as cipher, cipher-authentication chaining, and aead encryption and
decryption. This is achieved by calling DPDK Cryptodev APIs.
doc: add crypto port and action for pipeline in release notes This patch updates the release notes for added feature of crypto port and symmetric crypto action. Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
2018-10-12 08:38:04 +00:00
* **Added cryptodev port to port library.**
Cryptodev port is a shim layer in the port library that interacts with DPDK
Cryptodev PMDs including burst enqueuing and dequeuing crypto operations.
* **Added symmetric cryptographic actions to the pipeline library.**
In the pipeline library an added symmetric crypto action parsing and action
handler are implemented. The action allows automatically preparing the crypto
operation with the rules specified such as algorithm, key, and IV, etc for
the cryptodev port to process.
common/qat: support GEN3 devices This adds pci detection, queue-pair configuration and documentation for Intel GEN3 QuickAssist devices. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
2018-10-01 21:17:44 +00:00
* **Added support for GEN3 devices to Intel QAT driver .**
Added support for the third generation of Intel QuickAssist devices.
crypto/qat: support AES-CMAC This patch add AES-CMAC support. CMAC is a keyed hash function that is based on a symmetric key block cipher. It is One-Key CBC MAC improvement over XCBC-MAC. RFC 4493. NIST SP 800-38B. Signed-off-by: Tomasz Cel <tomaszx.cel@intel.com> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
2018-10-09 16:08:10 +00:00
* **Updated the QAT PMD.**
The QAT PMD was updated with additional support for:
* AES-CMAC algorithm.
crypto/aesni_mb: support AES-GCM algorithm This patch updates the current AESNI-MB PMD with added AES-GCM algorithm support. The patch includes the necessary changes to the code including the capability update, control and data patch changes for the AES-GCM algorithm support. Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
2018-10-10 11:04:41 +00:00
* **Updated the AESNI MB PMD.**
The AESNI MB PMD has been updated with additional support for AES-GCM
algorithm support.
doc: add CAAM JR guide add caam jr driver details, supported features and algorithms in the document. release note and MAINTAINERS are also updated. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-10-16 12:48:57 +00:00
* **Added NXP CAAM JR PMD.**
Added the new caam job ring driver for NXP platforms. See the
"NXP CAAM JOB RING (caam_jr)" document for more details on this new driver.
compress/qat: enable dynamic huffman encoding Enable dynamic huffman encoding in the QAT comp PMD. Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
2018-10-26 18:18:30 +00:00
* **Added support for Dynamic Huffman Encoding to Intel QAT comp PMD.**
The Intel QuickAssist (QAT) compression PMD has been updated with support
for Dynamic Huffman Encoding for the Deflate algorithm.
doc: add event eth Tx adapter guide Add programmer's guide doc to explain the use of the Event Ethernet Tx Adapter library. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-20 17:41:16 +00:00
* **Added Event Ethernet Tx Adapter.**
Added event ethernet Tx adapter library that provides configuration and
data path APIs for the ethernet transmit stage of an event driven packet
processing application. These APIs abstract the implementation of the
transmit stage and allow the application to use eventdev PMD support or
a common implementation.
event/dsw: add documentation The DSW event device is documented in DPDK Programmer's Guide. The MAINTAINERS file and the 18.11 release notes are updated. Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-18 12:45:14 +00:00
* **Added Distributed Software Eventdev PMD.**
Added the new Distributed Software Event Device (DSW), which is a
pure-software eventdev driver distributing the work of scheduling
among all eventdev ports and the lcores using them. DSW, compared to
the SW eventdev PMD, sacrifices load balancing performance to
gain better event scheduling throughput and scalability.
hash: add extendable bucket feature In use cases that hash table capacity needs to be guaranteed, the extendable bucket feature can be used to contain extra keys in linked lists when conflict happens. This is similar concept to the extendable bucket hash table in packet framework. This commit adds the extendable bucket feature. User can turn it on or off through the extra flag field during table creation time. Extendable bucket table composes of buckets that can be linked list to current main table. When extendable bucket is enabled, the hash table load can always achieve 100%. In other words, the table can always accommodate the same number of keys as the specified table size. This provides 100% table capacity guarantee. Although keys ending up in the ext buckets may have longer look up time, they should be rare due to the cuckoo algorithm. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Acked-by: Dharmik Thakkar <dharmik.thakkar@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2018-10-22 18:39:46 +00:00
* **Added extendable bucket feature to hash library (rte_hash).**
This new “extendable bucket” feature provides 100% insertion guarantee to
the capacity specified by the user by extending hash table with extra
buckets when needed to accommodate the unlikely event of intensive hash
hash: use partial-key hashing This commit changes the hashing mechanism to "partial-key hashing" to calculate bucket index and signature of key. This is proposed in Bin Fan, et al's paper "MemC3: Compact and Concurrent MemCache with Dumber Caching and Smarter Hashing". Basically the idea is to use "xor" to derive alternative bucket from current bucket index and signature. With "partial-key hashing", it reduces the bucket memory requirement from two cache lines to one cache line, which improves the memory efficiency and thus the lookup speed. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Dharmik Thakkar <dharmik.thakkar@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2018-10-22 18:39:48 +00:00
collisions. In addition, the internal hashing algorithm was changed to use
partial-key hashing to improve memory efficiency and lookup performance.
hash: add extendable bucket feature In use cases that hash table capacity needs to be guaranteed, the extendable bucket feature can be used to contain extra keys in linked lists when conflict happens. This is similar concept to the extendable bucket hash table in packet framework. This commit adds the extendable bucket feature. User can turn it on or off through the extra flag field during table creation time. Extendable bucket table composes of buckets that can be linked list to current main table. When extendable bucket is enabled, the hash table load can always achieve 100%. In other words, the table can always accommodate the same number of keys as the specified table size. This provides 100% table capacity guarantee. Although keys ending up in the ext buckets may have longer look up time, they should be rare due to the cuckoo algorithm. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Acked-by: Dharmik Thakkar <dharmik.thakkar@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2018-10-22 18:39:46 +00:00
hash: add lock-free r/w concurrency Add lock-free read-write concurrency. This is achieved by the following changes. 1) Add memory ordering to avoid race conditions. The only race condition that can occur is - using the key store element before the key write is completed. Hence, while inserting the element the release memory order is used. Any other race condition is caught by the key comparison. Memory orderings are added only where needed. For ex: reads in the writer's context do not need memory ordering as there is a single writer. key_idx in the bucket entry and pdata in the key store element are used for synchronisation. key_idx is used to release an inserted entry in the bucket to the reader. Use of pdata for synchronisation is required due to updation of an existing entry where-in only the pdata is updated without updating key_idx. 2) Reader-writer concurrency issue, caused by moving the keys to their alternative locations during key insert, is solved by introducing a global counter(tbl_chng_cnt) indicating a change in table. 3) Add the flag to enable reader-writer concurrency during run time. Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Yipeng Wang <yipeng1.wang@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2018-10-26 05:37:32 +00:00
* **Added lock free reader/writer concurrency to hash library (rte_hash).**
Lock free reader/writer concurrency prevents the readers from getting
blocked due to a pre-empted writer thread. This allows the hash library
to be used in scenarios where the writer thread runs on control plane.
power: add traffic pattern aware power control 1. Abstract For packet processing workloads such as DPDK polling is continuous. This means CPU cores always show 100% busy independent of how much work those cores are doing. It is critical to accurately determine how busy a core is hugely important for the following reasons: * No indication of overload conditions. * User does not know how much real load is on a system, resulting in wasted energy as no power management is utilized. Compared to the original l3fwd-power design, instead of going to sleep after detecting an empty poll, the new mechanism just lowers the core frequency. As a result, the application does not stop polling the device, which leads to improved handling of bursts of traffic. When the system become busy, the empty poll mechanism can also increase the core frequency (including turbo) to do best effort for intensive traffic. This gives us more flexible and balanced traffic awareness over the standard l3fwd-power application. 2. Proposed solution The proposed solution focuses on how many times empty polls are executed. The less the number of empty polls, means current core is busy with processing workload, therefore, the higher frequency is needed. The high empty poll number indicates the current core not doing any real work therefore, we can lower the frequency to safe power. In the current implementation, each core has 1 empty-poll counter which assume 1 core is dedicated to 1 queue. This will need to be expanded in the future to support multiple queues per core. 2.1 Power state definition: LOW: Not currently used, reserved for future use. MED: the frequency is used to process modest traffic workload. HIGH: the frequency is used to process busy traffic workload. 2.2 There are two phases to establish the power management system: a.Initialization/Training phase. The training phase is necessary in order to figure out the system polling baseline numbers from idle to busy. The highest poll count will be during idle, where all polls are empty. These poll counts will be different between systems due to the many possible processor micro-arch, cache and device configurations, hence the training phase. In the training phase, traffic is blocked so the training algorithm can average the empty-poll numbers for the LOW, MED and HIGH power states in order to create a baseline. The core's counter are collected every 10ms, and the Training phase will take 2 seconds. Training is disabled as default configuration. The default parameter is applied. Sample App still can trigger training if that's needed. Once the training phase has been executed once on a system, the application can then be started with the relevant thresholds provided on the command line, allowing the application to start passing start traffic immediately b.Normal phase. Traffic starts immediately based on the default thresholds, or based on the user supplied thresholds via the command line parameters. The run-time poll counts are compared with the baseline and the decision will be taken to move to MED power state or HIGH power state. The counters are calculated every 10ms. 3. Proposed API 1. rte_power_empty_poll_stat_init(struct ep_params **eptr, uint8_t *freq_tlb, struct ep_policy *policy); which is used to initialize the power management system.   2. rte_power_empty_poll_stat_free(void); which is used to free the resource hold by power management system.   3. rte_power_empty_poll_stat_update(unsigned int lcore_id); which is used to update specific core empty poll counter, not thread safe   4. rte_power_poll_stat_update(unsigned int lcore_id, uint8_t nb_pkt); which is used to update specific core valid poll counter, not thread safe   5. rte_power_empty_poll_stat_fetch(unsigned int lcore_id); which is used to get specific core empty poll counter.   6. rte_power_poll_stat_fetch(unsigned int lcore_id); which is used to get specific core valid poll counter. 7. rte_empty_poll_detection(struct rte_timer *tim, void *arg); which is used to detect empty poll state changes then take action. Signed-off-by: Liang Ma <liang.j.ma@intel.com> Reviewed-by: Lei Yao <lei.a.yao@intel.com> Acked-by: David Hunt <david.hunt@intel.com>
2018-10-19 11:07:18 +00:00
* **Added Traffic Pattern Aware Power Control Library**
Added an experimental library. This extend Power Library and provide
empty_poll APIs. This feature measure how many times empty_poll are
executed per core, use the number of empty polls as a hint for system
power management.
See the :doc:`../prog_guide/power_man` section of the DPDK Programmers
Guide document for more information.
examples/power: add JSON string handling Add JSON string handling to vm_power_manager for JSON strings received through the fifo. The format of the JSON strings are detailed in the next patch, the vm_power_manager user guide documentation updates. This patch introduces a new dependency on Jansson, a C library for encoding, decoding and manipulating JSON data. To compile the sample app you now need to have installed libjansson4 and libjansson-dev (these may be named slightly differently depending on your Operating System) Signed-off-by: David Hunt <david.hunt@intel.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-17 13:05:31 +00:00
* **Added JSON power policy interface for containers.**
Extended the Power Library and vm_power_manager sample app to allow power
policies to be submitted via a FIFO using JSON formatted strings. Previously
limited to Virtual Machines, this feature extends power policy functionality
to containers and host applications that need to have their cores frequency
controlled based on the rules contained in the policy.
doc: add telemetry how-to This patch adds all documentation for telemetry. A description on how to use the Telemetry API with a DPDK application is given in this document. It also adds a release notes update for telemetry. Signed-off-by: Ciara Power <ciara.power@intel.com> Signed-off-by: Brian Archbold <brian.archbold@intel.com> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
2018-10-27 09:17:48 +00:00
* **Added Telemetry API.**
Added the telemetry API which allows applications to transparently expose
their telemetry via a UNIX socket in JSON. The JSON can be consumed by any
Service Assurance agent, such as CollectD.
doc: add new KNI features to release notes Add the new module parameter for the KNI kernel module, the new command line flag for the KNI sample application, and the new API function 'rte_kni_update_link()' to the release note. Fixes: c6fd54f28c24 ("kni: add function to set link state on kernel interface") Fixes: 89397a01ce4a ("kni: set default carrier state of interface") Fixes: 724beb913b44 ("examples/kni: monitor and update link state continually") Signed-off-by: Dan Gora <dg@adax.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-11-05 19:54:13 +00:00
* **Updated KNI kernel module, rte_kni library, and KNI sample application.**
Updated the KNI kernel module with a new kernel module parameter,
``carrier=[on|off]`` to allow the user to control the default carrier
state of KNI kernel network interfaces. The default carrier state
is now set to ``off``, so the interfaces cannot be used until the
carrier state is set to ``on`` via ``rte_kni_update_link`` or
by writing ``1`` to ``/sys/devices/virtual/net/<iface>/carrier``.
In previous versions the default carrier state was left undefined.
See :doc:`../prog_guide/kernel_nic_interface` for more information.
Added the new API function ``rte_kni_update_link`` to allow the user
to set the carrier state of the KNI kernel network interface.
Added a new command line flag ``-m`` to the KNI sample application to
monitor and automatically reflect the physical NIC carrier state to the
KNI kernel network interface with the new ``rte_kni_update_link`` API.
See :doc:`../sample_app_ug/kernel_nic_interface` for more information.
app/testpmd: add queue deferred start switch Signed-off-by: Ian Dolzhansky <ian.dolzhansky@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2018-09-20 13:55:49 +00:00
* **Added ability to switch queue deferred start flag on testpmd app.**
Added a console command to testpmd app, giving ability to switch
``rx_deferred_start`` or ``tx_deferred_start`` flag of the specified queue of
the specified port. The port must be stopped before the command call in order
to reconfigure queues.
examples/vdpa: introduce a new sample for vDPA The vdpa sample application creates vhost-user sockets by using the vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes virtio ring compatible devices to serve virtio driver directly to enable datapath acceleration. As vDPA driver can help to set up vhost datapath, this application doesn't need to launch dedicated worker threads for vhost enqueue/dequeue operations. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Xiao Wang <xiao.w.wang@intel.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2018-09-28 21:47:47 +00:00
* **Add a new sample for vDPA**
The vdpa sample application creates vhost-user sockets by using the
vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes
virtio ring compatible devices to serve virtio driver directly to enable
datapath acceleration. As vDPA driver can help to set up vhost datapath,
this application doesn't need to launch dedicated worker threads for vhost
enqueue/dequeue operations.
examples/fips_validation: add crypto FIPS application Added FIPS application into the examples to allow users to use a simple sample app to validate their systems and be able to get FIPS certification. Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com> Reviewed-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-11-02 09:55:28 +00:00
* **Added cryptodev FIPS validation example application.**
Added an example application to parse and perform symmetric cryptography
computation to the NIST Cryptographic Algorithm Validation Program (CAVP)
test vectors.
test: allow taking extra arguments from environment When running unit tests automatically, either via script, from meson, or otherwise, the same set of options may be used for each run, for example to set a standard coremask to be used for all tests. To facilitate this, this patch adds support for the test binary taking additional EAL parameters from the environment and appending them to the argc/argv list passed to eal init. This allows parameter modification without having to edit test scripts etc. There are now two environment variables which can be used for running tests: * DPDK_TEST - (added previously) passes the test name to be run automatically rather than running the app interactively. Used by "meson test" when running tests individually or as part of a suite. * DPDK_TEST_PARAMS - new parameter to specify the commandline arguments to use with the test binary. For example to run a test, or tests, on only 16 lcores, and to skip pci scan we can set this to "-l 0-15 --no-pci". Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Tested-by: Luca Boccassi <bluca@debian.org>
2018-10-12 15:34:04 +00:00
* **Allow unit test binary to take parameters from the environment**
The unit test "test", or "dpdk-test", binary is often called from scripts,
which can make passing additional parameters, such as a coremask, to it more
awkward. Support has been added to the application to allow it to take
additional command-line parameter values from the "DPDK_TEST_PARAMS"
environment variable to make this application easier to use.
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
API Changes
-----------
.. This section should contain API changes. Sample format:
* Add a short 1-2 sentence description of the API change.
Use fixed width quotes for ``function_names`` or ``struct_names``.
Use the past tense.
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
mem: allow memseg lists to be marked as external When we allocate and use DPDK memory, we need to be able to differentiate between DPDK hugepage segments and segments that were made part of DPDK but are externally allocated. Add such a property to memseg lists. This breaks the ABI, so document the change in release notes. This also breaks a few internal assumptions about memory contiguousness, so adjust malloc code in a few places. All current calls for memseg walk functions were adjusted to ignore external segments where it made sense. Mempools is a special case, because we may be asked to allocate a mempool on a specific socket, and we need to ignore all page sizes on other heaps or other sockets. Previously, this assumption of knowing all page sizes was not a problem, but it will be now, so we have to match socket ID with page size when calculating minimum page size for a mempool. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Yongseok Koh <yskoh@mellanox.com>
2018-10-02 13:34:40 +00:00
* eal: ``rte_memseg_list`` structure now has an additional flag indicating
whether the memseg list is externally allocated. This will have implications
for any users of memseg-walk-related functions, as they will now have to skip
externally allocated segments in most cases if the intent is to only iterate
over internal DPDK memory.
mem: do not check for invalid socket ID We will be assigning "invalid" socket ID's to external heap, and malloc will now be able to verify if a supplied socket ID is in fact a valid one, rendering parameter checks for sockets obsolete. This changes the semantics of what we understand by "socket ID", so document the change in the release notes. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-02 13:34:42 +00:00
``socket_id`` parameter across the entire DPDK has gained additional meaning,
as some socket ID's will now be representing externally allocated memory. No
changes will be required for existing code as backwards compatibility will be
kept, and those who do not use this feature will not see these extra socket
ID's. Any new API's must not check socket ID parameters themselves, and must
instead leave it to the memory subsystem to decide whether socket ID is a
valid one.
mem: allow memseg lists to be marked as external When we allocate and use DPDK memory, we need to be able to differentiate between DPDK hugepage segments and segments that were made part of DPDK but are externally allocated. Add such a property to memseg lists. This breaks the ABI, so document the change in release notes. This also breaks a few internal assumptions about memory contiguousness, so adjust malloc code in a few places. All current calls for memseg walk functions were adjusted to ignore external segments where it made sense. Mempools is a special case, because we may be asked to allocate a mempool on a specific socket, and we need to ignore all page sizes on other heaps or other sockets. Previously, this assumption of knowing all page sizes was not a problem, but it will be now, so we have to match socket ID with page size when calculating minimum page size for a mempool. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Yongseok Koh <yskoh@mellanox.com>
2018-10-02 13:34:40 +00:00
devargs: remove deprecated functions rte_eal_parse_devargs_str() does not support parsing the bus name at the start of devargs. So it was renamed and deprecated. rte_eal_devargs_add(), rte_eal_devargs_type_count() and rte_eal_devargs_dump() were declared deprecated and had their implementation body renamed. All these functions were deprecated in release 18.05. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2018-09-19 22:58:58 +00:00
* eal: The following devargs functions, which were deprecated in 18.05,
were removed in 18.11:
``rte_eal_parse_devargs_str()``, ``rte_eal_devargs_add()``,
``rte_eal_devargs_type_count()``, and ``rte_eal_devargs_dump()``.
devargs: simplify parameters of removal function The function rte_devargs_remove(), which is intended to be internal, can take a devargs structure as argument. The matching is still using string comparison of bus name and device name. It is simpler and may allow a different devargs matching in future. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2018-09-19 21:55:01 +00:00
* eal: The parameters of the function ``rte_devargs_remove()`` have changed
from bus and device names to ``struct rte_devargs``.
eal: remove deprecated attach/detach functions These hotplug functions were deprecated and have some new replacements. As announced earlier, the oldest ones are now removed. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-23 08:28:41 +00:00
* eal: The deprecated functions attach/detach were removed in 18.11.
``rte_eal_dev_attach`` can be replaced by
``rte_dev_probe`` or ``rte_eal_hotplug_add``.
``rte_eal_dev_detach`` can be replaced by
``rte_dev_remove`` or ``rte_eal_hotplug_remove``.
eal: enable hotplug on multi-process We are going to introduce the solution to handle hotplug in multi-process, it includes the below scenario: 1. Attach a device from the primary 2. Detach a device from the primary 3. Attach a device from a secondary 4. Detach a device from a secondary In the primary-secondary process model, we assume devices are shared by default. that means attaches or detaches a device on any process will broadcast to all other processes through mp channel then device information will be synchronized on all processes. Any failure during attaching/detaching process will cause inconsistent status between processes, so proper rollback action should be considered. This patch covers the implementation of case 1,2. Case 3,4 will be implemented on a separate patch. IPC scenario for Case 1, 2: attach a device a) primary attach the new device if failed goto h). b) primary send attach sync request to all secondary. c) secondary receive request and attach the device and send a reply. d) primary check the reply if all success goes to i). e) primary send attach rollback sync request to all secondary. f) secondary receive the request and detach the device and send a reply. g) primary receive the reply and detach device as rollback action. h) attach fail i) attach success detach a device a) primary send detach sync request to all secondary b) secondary detach the device and send reply c) primary check the reply if all success goes to f). d) primary send detach rollback sync request to all secondary. e) secondary receive the request and attach back device. goto g) f) primary detach the device if success goto g), else goto d) g) detach fail. h) detach success. Signed-off-by: Qi Zhang <qi.z.zhang@intel.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-16 00:16:28 +00:00
* eal: The scope of ``rte_eal_hotplug_add()``/``rte_dev_probe()``
and ``rte_eal_hotplug_remove()``/``rte_dev_remove()`` is extended.
In multi-process model, they will guarantee that the device is
attached or detached on all processes.
mbuf: remove deprecated segment free functions __rte_mbuf_raw_free and __rte_pktmbuf_prefree_seg have been deprecated for a long time now (early 17.05), are not part of the abi and are easily replaced with existing api. Signed-off-by: David Marchand <david.marchand@6wind.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-09-17 12:45:09 +00:00
* mbuf: The ``__rte_mbuf_raw_free()`` and ``__rte_pktmbuf_prefree_seg()``
functions were deprecated since 17.05 and are replaced by
``rte_mbuf_raw_free()`` and ``rte_pktmbuf_prefree_seg()``.
ethdev: remove deprecated attach/detach functions The hotplug attach/detach features are implemented in EAL layer. There is a new ethdev iterator to retrieve ports from ethdev layer. As announced earlier, the (buggy) ethdev functions are now removed. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-23 08:28:40 +00:00
* ethdev: The deprecated functions attach/detach were removed in 18.11.
``rte_eth_dev_attach`` can be replaced by ``RTE_ETH_FOREACH_MATCHING_DEV``
and ``rte_dev_probe`` or ``rte_eal_hotplug_add``.
``rte_eth_dev_detach`` can be replaced by
``rte_dev_remove`` or ``rte_eal_hotplug_remove``.
ethdev: complete closing of port After closing a port, it cannot be restarted. So there is no reason to not free all associated resources. The last step was done with rte_eth_dev_detach() which is deprecated. Instead of blindly removing the associated rte_device, the driver should check if no more port (ethdev, cryptodev, etc) is open for the device. The last ethdev freeing which were done by rte_eth_dev_detach(), are now done at the end of rte_eth_dev_close() if the driver supports the flag RTE_ETH_DEV_CLOSE_REMOVE. There will be a transition period for PMDs to enable this new flag and migrate to the new behaviour. When enabling RTE_ETH_DEV_CLOSE_REMOVE, the PMD must free all its private resources for the port, in its dev_close function. It is advised to call the dev_close function in the remove function in order to support removing a device without closing its ports. Some drivers does not allocate MAC addresses dynamically or separately. In those cases, the pointer is set to NULL, in order to avoid wrongly freeing them in rte_eth_dev_release_port(). A closed port will have the state RTE_ETH_DEV_UNUSED which is considered as invalid by rte_eth_dev_is_valid_port(). So validity is not checked anymore for closed ports in testpmd. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-10-19 02:07:57 +00:00
* ethdev: A call to ``rte_eth_dev_release_port()`` has been added in
``rte_eth_dev_close()``. As a consequence, a closed port is freed
and seen as invalid because of its state ``RTE_ETH_DEV_UNUSED``.
This new behaviour is enabled per driver for a migration period.
ethdev: fix MAC changes when live change not supported Current code assumes a MAC change can occur when the port has been started. In fact, there are some NICs which require this port state for being successful, but other NICs not always support MAC change in that case. This patch supports a new device flag for a device advertising this limitation, and if the flag is set, the MAC is changed before the port starts. Fixes: af75078fece3 ("first public release") Cc: stable@dpdk.org Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-08-24 14:25:35 +00:00
* A new device flag, RTE_ETH_DEV_NOLIVE_MAC_ADDR, changes the order of
actions inside rte_eth_dev_start regarding MAC set. Some NICs do not
support MAC changes once the port has started and with this new device
flag the MAC can be properly configured in any case. This is particularly
important for bonding.
doc: announce CRC strip changes in release notes Document changes done in commit 323e7b667f18 ("ethdev: make default behavior CRC strip on Rx") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: David Marchand <david.marchand@6wind.com>
2018-09-24 17:31:40 +00:00
* The default behaviour of CRC strip offload changed. Without any specific Rx
offload flag, default behavior by PMD is now to strip CRC.
DEV_RX_OFFLOAD_CRC_STRIP offload flag has been removed.
To request keeping CRC, application should set ``DEV_RX_OFFLOAD_KEEP_CRC`` Rx
offload.
eventdev: fix port id argument in Rx adapter caps Make the ethernet port id passed into rte_event_eth_rx_adapter_caps_get() 16 bit. Also, update the event rx adapter test to use 16 bit ethernet port ids. Fixes: c2189c907dd1 ("eventdev: make ethdev port identifiers 16-bit") Cc: stable@dpdk.org Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-25 09:49:05 +00:00
* eventdev: Type of 2nd parameter to ``rte_event_eth_rx_adapter_caps_get()``
has been changed from uint8_t to uint16_t.
doc: add KNI behaviour change in release notes Commit 89397a01ce4a ("kni: set default carrier state of interface") changes the KNI interface default carrier status. Which prevents traffic flow by default and may break some existing usage / testing. Document this behavior change in release notes. Fixes: c6fd54f28c24 ("kni: add function to set link state on kernel interface") Fixes: 89397a01ce4a ("kni: set default carrier state of interface") Fixes: 724beb913b44 ("examples/kni: monitor and update link state continually") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-11-05 17:28:44 +00:00
* kni: By default, interface carrier status is ``off`` which means there won't
be any traffic. It can be set to ``on`` via ``rte_kni_update_link()`` API
or via ``sysfs`` interface:
``echo 1 > /sys/class/net/vEth0/carrier``.
Note interface should be ``up`` to be able to read/write sysfs interface.
When KNI sample application is used, ``-m`` parameter can be used to
automatically update the carrier status for the interface.
doc: add KNI limitation in release notes Commit a9460a0b2efb ("kni: fix build on Linux 4.19") disables some ethtool commands because they are removed in newer (4.19) kernels. This patch documents removed functionality. Fixes: a9460a0b2efb ("kni: fix build on Linux 4.19") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-11-05 17:09:40 +00:00
* kni: When ethtool support enabled (``CONFIG_RTE_KNI_KMOD_ETHTOOL=y``)
ethtool commands ``ETHTOOL_GSET & ETHTOOL_SSET`` are no more supported for the
kernels that has ``ETHTOOL_GLINKSETTINGS & ETHTOOL_SLINKSETTINGS`` support.
This means ``ethtool "-a|--show-pause", "-s|--change"`` won't work, and
``ethtool <iface>`` output will have less information.
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
ABI Changes
-----------
.. This section should contain ABI changes. Sample format:
* Add a short 1-2 sentence description of the ABI change
that was announced in the previous releases and made in this release.
Use fixed width quotes for ``function_names`` or ``struct_names``.
Use the past tense.
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
mem: store memory mode flags in shared config Currently, command-line switches for legacy mem mode or single-file segments mode are only stored in internal config. This leads to a situation where these flags have to always match between primary and secondary, which is bad for usability. Fix this by storing these flags in the shared config as well, so that secondary process can know if the primary was launched in single-file segments or legacy mem mode. This bumps the EAL ABI, however there's an EAL deprecation notice already in place[1] for a different feature, so that's OK. [1] http://patches.dpdk.org/patch/43502/ Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-09-20 15:41:26 +00:00
* eal: added ``legacy_mem`` and ``single_file_segments`` values to
``rte_config`` structure on account of improving DPDK usability when
using either ``--legacy-mem`` or ``--single-file-segments`` flags.
mem: add length to memseg list Previously, to calculate length of memory area covered by a memseg list, we would've needed to multiply page size by length of fbarray backing that memseg list. This is not obvious and unnecessarily low level, so store length in the memseg list itself. This breaks ABI, so bump the EAL ABI version and document the change. Also, while we're breaking ABI, pack the members a little better. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-10-02 13:34:39 +00:00
* eal: EAL library ABI version was changed due to previously announced work on
supporting external memory in DPDK:
- structure ``rte_memseg_list`` now has a new field indicating length
of memory addressed by the segment list
mem: allow memseg lists to be marked as external When we allocate and use DPDK memory, we need to be able to differentiate between DPDK hugepage segments and segments that were made part of DPDK but are externally allocated. Add such a property to memseg lists. This breaks the ABI, so document the change in release notes. This also breaks a few internal assumptions about memory contiguousness, so adjust malloc code in a few places. All current calls for memseg walk functions were adjusted to ignore external segments where it made sense. Mempools is a special case, because we may be asked to allocate a mempool on a specific socket, and we need to ignore all page sizes on other heaps or other sockets. Previously, this assumption of knowing all page sizes was not a problem, but it will be now, so we have to match socket ID with page size when calculating minimum page size for a mempool. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Yongseok Koh <yskoh@mellanox.com>
2018-10-02 13:34:40 +00:00
- structure ``rte_memseg_list`` now has a new flag indicating whether
the memseg list refers to external memory
malloc: index heaps using heap ID rather than NUMA node Switch over all parts of EAL to use heap ID instead of NUMA node ID to identify heaps. Heap ID for DPDK-internal heaps is NUMA node's index within the detected NUMA node list. Heap ID for external heaps will be order of their creation. This breaks the ABI, so document the changes. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-02 13:34:41 +00:00
- structure ``rte_malloc_heap`` now has a new field indicating socket
ID the malloc heap belongs to
- structure ``rte_mem_config`` has had its ``malloc_heaps`` array
resized from ``RTE_MAX_NUMA_NODES`` to ``RTE_MAX_HEAPS`` value
malloc: add name to malloc heaps We will need to refer to external heaps in some way. While we use heap ID's internally, for external API use it has to be something more user-friendly. So, we will be using a string to uniquely identify a heap. This breaks the ABI, so document the change. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-02 13:34:46 +00:00
- structure ``rte_malloc_heap`` now has a ``heap_name`` member
malloc: allow creating malloc heaps Add API to allow creating new malloc heaps. They will be created with socket ID's going above RTE_MAX_NUMA_NODES, to avoid clashing with internal heaps. This breaks the ABI, so document the change. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-02 13:34:49 +00:00
- structure ``rte_eal_memconfig`` has been extended to contain next
socket ID for externally allocated segments
mem: add length to memseg list Previously, to calculate length of memory area covered by a memseg list, we would've needed to multiply page size by length of fbarray backing that memseg list. This is not obvious and unnecessarily low level, so store length in the memseg list itself. This breaks ABI, so bump the EAL ABI version and document the change. Also, while we're breaking ABI, pack the members a little better. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-10-02 13:34:39 +00:00
mem: add function for checking memseg IOVA A device can suffer addressing limitations. This function checks memsegs have iovas within the supported range based on dma mask. PMDs should use this function during initialization if device suffers addressing limitations, returning an error if this function returns memsegs out of range. Another usage is for emulated IOMMU hardware with addressing limitations. It is necessary to save the most restricted dma mask for checking out memory allocated dynamically after initialization. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-05 12:45:22 +00:00
* eal: Added ``dma_maskbits`` to ``rte_mem_config`` for keeping more restricted
dma mask based on devices addressing limitations.
eal: add bus pointer in device structure When a device is added with a devargs (hotplug or whitelist), the bus pointer can be retrieved via its devargs. But there is no such devargs.bus in case of standard scan. A pointer to the rte_bus handle is added to rte_device. When a device is allocated (during a scan), the pointer to its bus is assigned. It will make possible to remove a rte_device, using the function pointer from its bus. The function rte_bus_find_by_device() becomes useless, and may be removed later. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2018-10-02 22:25:06 +00:00
* eal: The structure ``rte_device`` got a new field to reference a ``rte_bus``.
It is changing the size of the ``struct rte_device`` and the inherited
device structures of all buses.
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
Removed Items
-------------
.. This section should contain removed items in this release. Sample format:
* Add a short 1-2 sentence description of the removed item
in the past tense.
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
Shared Library Versions
-----------------------
.. Update any library version updated in this release
and prepend with a ``+`` sign, like this:
librte_acl.so.2
+ librte_cfgfile.so.2
librte_cmdline.so.2
This section is a comment. Do not overwrite or remove it.
=========================================================
The libraries prepended with a plus sign were incremented in this version.
.. code-block:: diff
librte_acl.so.2
librte_bbdev.so.1
librte_bitratestats.so.2
librte_bpf.so.1
eal: add bus pointer in device structure When a device is added with a devargs (hotplug or whitelist), the bus pointer can be retrieved via its devargs. But there is no such devargs.bus in case of standard scan. A pointer to the rte_bus handle is added to rte_device. When a device is allocated (during a scan), the pointer to its bus is assigned. It will make possible to remove a rte_device, using the function pointer from its bus. The function rte_bus_find_by_device() becomes useless, and may be removed later. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2018-10-02 22:25:06 +00:00
+ librte_bus_dpaa.so.2
+ librte_bus_fslmc.so.2
+ librte_bus_ifpga.so.2
+ librte_bus_pci.so.2
+ librte_bus_vdev.so.2
+ librte_bus_vmbus.so.2
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
librte_cfgfile.so.2
librte_cmdline.so.2
librte_compressdev.so.1
librte_cryptodev.so.5
librte_distributor.so.1
mem: store memory mode flags in shared config Currently, command-line switches for legacy mem mode or single-file segments mode are only stored in internal config. This leads to a situation where these flags have to always match between primary and secondary, which is bad for usability. Fix this by storing these flags in the shared config as well, so that secondary process can know if the primary was launched in single-file segments or legacy mem mode. This bumps the EAL ABI, however there's an EAL deprecation notice already in place[1] for a different feature, so that's OK. [1] http://patches.dpdk.org/patch/43502/ Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-09-20 15:41:26 +00:00
+ librte_eal.so.9
doc: add missing shared library versions to release notes Fixes: 857ed6c68cf2 ("member: implement main API") Fixes: 56b6ef874f80 ("efd: new Elastic Flow Distributor library") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-15 14:50:52 +00:00
librte_efd.so.1
ethdev: add field for device data per process Primary and secondary processes share a per-device private data. With current design it is not possible to have data per-device per-process. This is required for handling properly the CPP interface inside the NFP PMD with multiprocess support. There is also at least another PMD driver, tap, with similar requirements for per-process device data. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-15 14:11:02 +00:00
+ librte_ethdev.so.11
eventdev: fix port id argument in Rx adapter caps Make the ethernet port id passed into rte_event_eth_rx_adapter_caps_get() 16 bit. Also, update the event rx adapter test to use 16 bit ethernet port ids. Fixes: c2189c907dd1 ("eventdev: make ethdev port identifiers 16-bit") Cc: stable@dpdk.org Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-25 09:49:05 +00:00
+ librte_eventdev.so.6
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
librte_flow_classify.so.1
librte_gro.so.1
librte_gso.so.1
librte_hash.so.2
librte_ip_frag.so.1
librte_jobstats.so.1
librte_kni.so.2
librte_kvargs.so.1
librte_latencystats.so.1
librte_lpm.so.2
librte_mbuf.so.4
doc: add missing shared library versions to release notes Fixes: 857ed6c68cf2 ("member: implement main API") Fixes: 56b6ef874f80 ("efd: new Elastic Flow Distributor library") Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-15 14:50:52 +00:00
librte_member.so.1
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
librte_mempool.so.5
librte_meter.so.2
librte_metrics.so.1
librte_net.so.1
librte_pci.so.1
librte_pdump.so.2
librte_pipeline.so.3
librte_pmd_bnxt.so.2
librte_pmd_bond.so.2
librte_pmd_i40e.so.2
librte_pmd_ixgbe.so.2
librte_pmd_dpaa2_qdma.so.1
librte_pmd_ring.so.2
librte_pmd_softnic.so.1
librte_pmd_vhost.so.2
librte_port.so.3
librte_power.so.1
librte_rawdev.so.1
librte_reorder.so.1
librte_ring.so.2
librte_sched.so.1
librte_security.so.1
librte_table.so.3
librte_timer.so.1
doc: fix vhost library version in release notes Fixes: 7c1290374621 ("vhost: rename device ops struct") Cc: stable@dpdk.org Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>
2018-10-15 14:50:54 +00:00
librte_vhost.so.4
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
Known Issues
------------
.. This section should contain new known issues in this release. Sample format:
* **Add title in present tense with full stop.**
Add a short 1-2 sentence description of the known issue
in the present tense. Add information on any known workarounds.
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
net/netvsc: support integrated VF Integrate accelerated networking support into netvsc PMD. This allows netvsc to manage VF without using failsafe or vdev_netvsc. For the exception vswitch path some tests like transmit get a 22% increase in packets/sec. For the VF path, the code is slightly shorter but has no real change in performance. Pro: * using netvsc is more like other DPDK NIC's * the exception packet uses less CPU * much smaller code size * no locking required on VF transmit/receive path * no legacy Linux network device to get mangled by userspace * much simpler (1K vs 9K) LOC * unified extended statistics Con: * using netvsc has more complex startup model * no bifurcated driver support * no flow support (since host does not have flow API). * no tunnel offload support * no receive interrupt support Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-08-30 22:35:12 +00:00
* When using SR-IOV (VF) support with netvsc PMD and the Mellanox mlx5 bifurcated
driver; the Linux netvsc device must be brought up before the netvsc device is
unbound and passed to the DPDK.
mem: fix anonymous mapping on Power9 Removed the use of MAP_HUGETLB for anonymous mapping on ppc64. The MAP_HUGETLB had previously been added to workaround issues on IBM Power8 systems when mapping /dev/zero. In the current code the MAP_HUGETLB flag will cause the anonymous mapping to fail on Power9. Note, Power8 is currently failing to correctly mmap Hugepages, with and without this change. Fixes: 284ae3e9ff9a ("eal/ppc: fix mmap for memory initialization") Signed-off-by: David Wilder <dwilder@us.ibm.com> Reviewed-by: Pradeep Satyanarayana <pradeep@us.ibm.com>
2018-11-16 17:35:38 +00:00
* IBM Power8 is not supported by this release of DPDK. IBM Power9 is supported.
version: 18.11-rc0 Start version numbering for a new release cycle, and introduce a template file for release notes. The release notes comments have a new block to suggest the order of items, inspired by Ferruh's proposal. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-08-11 21:58:03 +00:00
Tested Platforms
----------------
.. This section should contain a list of platforms that were tested
with this release.
The format is:
* <vendor> platform with <vendor> <type of devices> combinations
* List of CPU
* List of OS
* List of devices
* Other relevant details...
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
Reference in New Issue Copy Permalink