2017-05-11 13:57:45 +01:00
|
|
|
DPDK Release 17.08
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
.. **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_17_08.html
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
New Features
|
|
|
|
|
------------
|
|
|
|
|
|
|
|
|
|
.. This section should contain new features added in this release. Sample
|
|
|
|
|
format:
|
|
|
|
|
|
|
|
|
|
* **Add a title in the past tense with a full stop.**
|
|
|
|
|
|
|
|
|
|
Add a short 1-2 sentence description in the past tense. The description
|
|
|
|
|
should be enough to allow someone scanning the release notes to
|
|
|
|
|
understand the new feature.
|
|
|
|
|
|
|
|
|
|
If the feature adds a lot of sub-features you can use a bullet list like
|
|
|
|
|
this:
|
|
|
|
|
|
|
|
|
|
* Added feature foo to do something.
|
|
|
|
|
* Enhanced feature bar to do something else.
|
|
|
|
|
|
|
|
|
|
Refer to the previous release notes for examples.
|
|
|
|
|
|
|
|
|
|
This section is a comment. do not overwrite or remove it.
|
|
|
|
|
Also, make sure to start the actual text at the margin.
|
|
|
|
|
=========================================================
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Increase minimum x86 ISA version to SSE4.2.**
|
2017-08-03 15:44:48 +02:00
|
|
|
|
|
|
|
|
Starting with version 17.08, DPDK requires SSE4.2 to run on x86.
|
|
|
|
|
Previous versions required SSE3.
|
|
|
|
|
|
2017-07-11 15:19:27 +01:00
|
|
|
* **Added Service Core functionality.**
|
|
|
|
|
|
|
|
|
|
The service core functionality added to EAL allows DPDK to run services such
|
2017-08-04 15:20:12 +01:00
|
|
|
as software PMDs on lcores without the application manually running them. The
|
2017-07-11 15:19:27 +01:00
|
|
|
service core infrastructure allows flexibility of running multiple services
|
|
|
|
|
on the same service lcore, and provides the application with powerful APIs to
|
|
|
|
|
configure the mapping from service lcores to services.
|
|
|
|
|
|
lib/gro: support TCP/IPv4
In this patch, we introduce five APIs to support TCP/IPv4 GRO.
- gro_tcp4_reassemble: reassemble an inputted TCP/IPv4 packet.
- gro_tcp4_tbl_create: create a TCP/IPv4 reassembly table, which is used
to merge packets.
- gro_tcp4_tbl_destroy: free memory space of a TCP/IPv4 reassembly table.
- gro_tcp4_tbl_pkt_count: return the number of packets in a TCP/IPv4
reassembly table.
- gro_tcp4_tbl_timeout_flush: flush timeout packets from a TCP/IPv4
reassembly table.
TCP/IPv4 GRO API assumes all inputted packets are with correct IPv4
and TCP checksums. And TCP/IPv4 GRO API doesn't update IPv4 and TCP
checksums for merged packets. If inputted packets are IP fragmented,
TCP/IPv4 GRO API assumes they are complete packets (i.e. with L4
headers).
In TCP/IPv4 GRO, we use a table structure, called TCP/IPv4 reassembly
table, to reassemble packets. A TCP/IPv4 reassembly table includes a key
array and a item array, where the key array keeps the criteria to merge
packets and the item array keeps packet information.
One key in the key array points to an item group, which consists of
packets which have the same criteria value. If two packets are able to
merge, they must be in the same item group. Each key in the key array
includes two parts:
- criteria: the criteria of merging packets. If two packets can be
merged, they must have the same criteria value.
- start_index: the index of the first incoming packet of the item group.
Each element in the item array keeps the information of one packet. It
mainly includes three parts:
- firstseg: the address of the first segment of the packet
- lastseg: the address of the last segment of the packet
- next_pkt_index: the index of the next packet in the same item group.
All packets in the same item group are chained by next_pkt_index.
With next_pkt_index, we can locate all packets in the same item
group one by one.
To process an incoming packet needs three steps:
a. check if the packet should be processed. Packets with one of the
following properties won't be processed:
- FIN, SYN, RST, URG, PSH, ECE or CWR bit is set;
- packet payload length is 0.
b. traverse the key array to find a key which has the same criteria
value with the incoming packet. If find, goto step c. Otherwise,
insert a new key and insert the packet into the item array.
c. locate the first packet in the item group via the start_index in the
key. Then traverse all packets in the item group via next_pkt_index.
If find one packet which can merge with the incoming one, merge them
together. If can't find, insert the packet into this item group.
Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 13:46:45 +08:00
|
|
|
* **Added Generic Receive Offload API.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Added Generic Receive Offload (GRO) API support to reassemble TCP/IPv4
|
|
|
|
|
packets. The GRO API assumes all input packets have the correct
|
lib/gro: support TCP/IPv4
In this patch, we introduce five APIs to support TCP/IPv4 GRO.
- gro_tcp4_reassemble: reassemble an inputted TCP/IPv4 packet.
- gro_tcp4_tbl_create: create a TCP/IPv4 reassembly table, which is used
to merge packets.
- gro_tcp4_tbl_destroy: free memory space of a TCP/IPv4 reassembly table.
- gro_tcp4_tbl_pkt_count: return the number of packets in a TCP/IPv4
reassembly table.
- gro_tcp4_tbl_timeout_flush: flush timeout packets from a TCP/IPv4
reassembly table.
TCP/IPv4 GRO API assumes all inputted packets are with correct IPv4
and TCP checksums. And TCP/IPv4 GRO API doesn't update IPv4 and TCP
checksums for merged packets. If inputted packets are IP fragmented,
TCP/IPv4 GRO API assumes they are complete packets (i.e. with L4
headers).
In TCP/IPv4 GRO, we use a table structure, called TCP/IPv4 reassembly
table, to reassemble packets. A TCP/IPv4 reassembly table includes a key
array and a item array, where the key array keeps the criteria to merge
packets and the item array keeps packet information.
One key in the key array points to an item group, which consists of
packets which have the same criteria value. If two packets are able to
merge, they must be in the same item group. Each key in the key array
includes two parts:
- criteria: the criteria of merging packets. If two packets can be
merged, they must have the same criteria value.
- start_index: the index of the first incoming packet of the item group.
Each element in the item array keeps the information of one packet. It
mainly includes three parts:
- firstseg: the address of the first segment of the packet
- lastseg: the address of the last segment of the packet
- next_pkt_index: the index of the next packet in the same item group.
All packets in the same item group are chained by next_pkt_index.
With next_pkt_index, we can locate all packets in the same item
group one by one.
To process an incoming packet needs three steps:
a. check if the packet should be processed. Packets with one of the
following properties won't be processed:
- FIN, SYN, RST, URG, PSH, ECE or CWR bit is set;
- packet payload length is 0.
b. traverse the key array to find a key which has the same criteria
value with the incoming packet. If find, goto step c. Otherwise,
insert a new key and insert the packet into the item array.
c. locate the first packet in the item group via the start_index in the
key. Then traverse all packets in the item group via next_pkt_index.
If find one packet which can merge with the incoming one, merge them
together. If can't find, insert the packet into this item group.
Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 13:46:45 +08:00
|
|
|
checksums. GRO API doesn't update checksums for merged packets. If
|
2017-08-04 15:20:12 +01:00
|
|
|
input packets are IP fragmented, the GRO API assumes they are complete
|
lib/gro: support TCP/IPv4
In this patch, we introduce five APIs to support TCP/IPv4 GRO.
- gro_tcp4_reassemble: reassemble an inputted TCP/IPv4 packet.
- gro_tcp4_tbl_create: create a TCP/IPv4 reassembly table, which is used
to merge packets.
- gro_tcp4_tbl_destroy: free memory space of a TCP/IPv4 reassembly table.
- gro_tcp4_tbl_pkt_count: return the number of packets in a TCP/IPv4
reassembly table.
- gro_tcp4_tbl_timeout_flush: flush timeout packets from a TCP/IPv4
reassembly table.
TCP/IPv4 GRO API assumes all inputted packets are with correct IPv4
and TCP checksums. And TCP/IPv4 GRO API doesn't update IPv4 and TCP
checksums for merged packets. If inputted packets are IP fragmented,
TCP/IPv4 GRO API assumes they are complete packets (i.e. with L4
headers).
In TCP/IPv4 GRO, we use a table structure, called TCP/IPv4 reassembly
table, to reassemble packets. A TCP/IPv4 reassembly table includes a key
array and a item array, where the key array keeps the criteria to merge
packets and the item array keeps packet information.
One key in the key array points to an item group, which consists of
packets which have the same criteria value. If two packets are able to
merge, they must be in the same item group. Each key in the key array
includes two parts:
- criteria: the criteria of merging packets. If two packets can be
merged, they must have the same criteria value.
- start_index: the index of the first incoming packet of the item group.
Each element in the item array keeps the information of one packet. It
mainly includes three parts:
- firstseg: the address of the first segment of the packet
- lastseg: the address of the last segment of the packet
- next_pkt_index: the index of the next packet in the same item group.
All packets in the same item group are chained by next_pkt_index.
With next_pkt_index, we can locate all packets in the same item
group one by one.
To process an incoming packet needs three steps:
a. check if the packet should be processed. Packets with one of the
following properties won't be processed:
- FIN, SYN, RST, URG, PSH, ECE or CWR bit is set;
- packet payload length is 0.
b. traverse the key array to find a key which has the same criteria
value with the incoming packet. If find, goto step c. Otherwise,
insert a new key and insert the packet into the item array.
c. locate the first packet in the item group via the start_index in the
key. Then traverse all packets in the item group via next_pkt_index.
If find one packet which can merge with the incoming one, merge them
together. If can't find, insert the packet into this item group.
Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 13:46:45 +08:00
|
|
|
packets (i.e. with L4 headers).
|
|
|
|
|
|
2017-08-04 17:33:04 +02:00
|
|
|
* **Added Fail-Safe PMD**
|
|
|
|
|
|
|
|
|
|
Added the new Fail-Safe PMD. This virtual device allows applications to
|
|
|
|
|
support seamless hotplug of devices.
|
|
|
|
|
See the :doc:`/nics/fail_safe` guide for more details about this driver.
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Added support for generic flow API (rte_flow) on igb NICs.**
|
2017-06-14 16:47:56 +08:00
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
This API provides a generic means of configuring hardware to match specific
|
|
|
|
|
ingress or egress traffic, altering its behavior and querying related counters
|
2017-06-14 16:47:56 +08:00
|
|
|
according to any number of user-defined rules.
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Added generic flow API support for Ethernet, IPv4, UDP, TCP and RAW pattern
|
|
|
|
|
items with QUEUE actions. There are four types of filter support for this
|
|
|
|
|
feature on igb.
|
2017-06-14 16:47:56 +08:00
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Added support for generic flow API (rte_flow) on enic.**
|
2017-05-17 15:38:11 -07:00
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Added flow API support for outer Ethernet, VLAN, IPv4, IPv6, UDP, TCP, SCTP,
|
|
|
|
|
VxLAN and inner Ethernet, VLAN, IPv4, IPv6, UDP and TCP pattern items with
|
|
|
|
|
QUEUE, MARK, FLAG and VOID actions for ingress traffic.
|
2017-05-17 15:38:11 -07:00
|
|
|
|
2017-05-27 09:16:16 +05:30
|
|
|
* **Added support for Chelsio T6 family of adapters**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
The CXGBE PMD was updated to run Chelsio T6 family of adapters.
|
2017-05-27 09:16:16 +05:30
|
|
|
|
2017-05-27 09:17:57 +05:30
|
|
|
* **Added latency and performance improvements for cxgbe**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
the Tx and Rx path in cxgbe were reworked to improve performance. In
|
|
|
|
|
addition the latency was reduced for slow traffic.
|
2017-05-27 09:17:57 +05:30
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Updated the bnxt PMD.**
|
|
|
|
|
|
|
|
|
|
Updated the bnxt PMD. The major enhancements include:
|
2017-06-01 12:07:23 -05:00
|
|
|
|
|
|
|
|
* Support MTU modification.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Add support for LRO.
|
|
|
|
|
* Add support for VLAN filter and strip functionality.
|
|
|
|
|
* Additional enhancements to add support for more dev_ops.
|
|
|
|
|
* Added PMD specific APIs mainly to control VF from PF.
|
2017-06-01 12:07:23 -05:00
|
|
|
* Update HWRM version to 1.7.7
|
|
|
|
|
|
2017-06-06 17:48:29 +03:00
|
|
|
* **Added support for Rx interrupts on mlx4 driver.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Rx queues can be now be armed with an interrupt which will trigger on the
|
2017-06-06 17:48:29 +03:00
|
|
|
next packet arrival.
|
|
|
|
|
|
2017-07-28 17:28:32 +03:00
|
|
|
* **Updated mlx5 driver.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Updated the mlx5 driver including the following changes:
|
2017-07-28 17:28:32 +03:00
|
|
|
|
|
|
|
|
* Added vectorized Rx/Tx burst for x86.
|
|
|
|
|
* Added support for isolated mode from flow API.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Reworked the flow drop action to implement in hardware classifier.
|
2017-07-28 17:28:32 +03:00
|
|
|
* Improved Rx interrupts management.
|
|
|
|
|
|
2017-06-12 14:03:22 +02:00
|
|
|
* **Updated szedata2 PMD.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Added support for firmware with multiple Ethernet ports per physical port.
|
2017-06-12 14:03:22 +02:00
|
|
|
|
2017-07-24 12:53:48 +05:30
|
|
|
* **Updated dpaa2 PMD.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Updated dpaa2 PMD. Major enhancements include:
|
|
|
|
|
|
|
|
|
|
* Added support for MAC Filter configuration.
|
|
|
|
|
* Added support for Segmented Buffers.
|
|
|
|
|
* Added support for VLAN filter and strip functionality.
|
|
|
|
|
* Additional enhancements to add support for more dev_ops.
|
2017-07-24 12:53:48 +05:30
|
|
|
* Optimized the packet receive path
|
|
|
|
|
|
2017-07-02 06:41:02 +01:00
|
|
|
* **Reorganized the symmetric crypto operation structure.**
|
|
|
|
|
|
|
|
|
|
The crypto operation (``rte_crypto_sym_op``) has been reorganized as follows:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* Removed the ``rte_crypto_sym_op_sess_type`` field.
|
|
|
|
|
* Replaced the pointer and physical address of IV with offset from the start
|
2017-07-02 06:41:13 +01:00
|
|
|
of the crypto operation.
|
2017-07-02 06:41:14 +01:00
|
|
|
* Moved length and offset of cipher IV to ``rte_crypto_cipher_xform``.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Removed "Additional Authentication Data" (AAD) length.
|
2017-07-02 06:41:18 +01:00
|
|
|
* Removed digest length.
|
2017-07-02 06:41:27 +01:00
|
|
|
* Removed AAD pointer and physical address from ``auth`` structure.
|
2017-07-02 06:41:21 +01:00
|
|
|
* Added ``aead`` structure, containing parameters for AEAD algorithms.
|
2017-07-02 06:41:02 +01:00
|
|
|
|
|
|
|
|
* **Reorganized the crypto operation structure.**
|
|
|
|
|
|
|
|
|
|
The crypto operation (``rte_crypto_op``) has been reorganized as follows:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* Added the ``rte_crypto_op_sess_type`` field.
|
|
|
|
|
* The enumerations ``rte_crypto_op_status`` and ``rte_crypto_op_type``
|
|
|
|
|
have been modified to be ``uint8_t`` values.
|
2017-07-02 06:41:04 +01:00
|
|
|
* Removed the field ``opaque_data``.
|
2017-07-02 06:41:05 +01:00
|
|
|
* Pointer to ``rte_crypto_sym_op`` has been replaced with a zero length array.
|
2017-07-02 06:41:02 +01:00
|
|
|
|
2017-07-05 06:26:14 +01:00
|
|
|
* **Reorganized the crypto symmetric session structure.**
|
|
|
|
|
|
|
|
|
|
The crypto symmetric session structure (``rte_cryptodev_sym_session``) has
|
|
|
|
|
been reorganized as follows:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* The ``dev_id`` field has been removed.
|
|
|
|
|
* The ``driver_id`` field has been removed.
|
|
|
|
|
* The mempool pointer ``mp`` has been removed.
|
2017-07-05 06:26:17 +01:00
|
|
|
* Replaced ``private`` marker with array of pointers to private data sessions
|
|
|
|
|
``sess_private_data``.
|
2017-07-05 06:26:14 +01:00
|
|
|
|
2017-07-02 06:41:20 +01:00
|
|
|
* **Updated cryptodev library.**
|
|
|
|
|
|
|
|
|
|
* Added AEAD algorithm specific functions and structures, so it is not
|
|
|
|
|
necessary to use a combination of cipher and authentication
|
|
|
|
|
structures anymore.
|
2017-06-30 15:34:21 +01:00
|
|
|
* Added helper functions for crypto device driver identification.
|
2017-07-05 06:26:17 +01:00
|
|
|
* Added support for multi-device sessions, so a single session can be
|
|
|
|
|
used in multiple drivers.
|
|
|
|
|
* Added functions to initialize and free individual driver private data
|
2017-08-04 15:20:12 +01:00
|
|
|
with the same session.
|
2017-07-02 06:41:20 +01:00
|
|
|
|
2017-07-03 18:01:39 +05:30
|
|
|
* **Updated dpaa2_sec crypto PMD.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Added support for AES-GCM and AES-CTR.
|
2017-07-03 18:01:39 +05:30
|
|
|
|
2017-07-02 03:55:05 +01:00
|
|
|
* **Updated the AESNI MB PMD.**
|
|
|
|
|
|
|
|
|
|
The AESNI MB PMD has been updated with additional support for:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* 12-byte IV on AES Counter Mode, apart from the previous 16-byte IV.
|
2017-07-02 03:55:05 +01:00
|
|
|
|
2017-07-04 01:12:40 +01:00
|
|
|
* **Updated the AES-NI GCM PMD.**
|
|
|
|
|
|
|
|
|
|
The AES-NI GCM PMD was migrated from the ISA-L library to the Multi Buffer
|
|
|
|
|
library, as the latter library has Scatter Gather List support
|
2017-08-04 15:20:12 +01:00
|
|
|
now. The migration entailed adding additional support for 192-bit keys.
|
2017-07-04 01:12:40 +01:00
|
|
|
|
2017-07-05 17:14:38 +01:00
|
|
|
* **Updated the Cryptodev Scheduler PMD.**
|
|
|
|
|
|
|
|
|
|
Added a multicore based distribution mode, which distributes the enqueued
|
|
|
|
|
crypto operations among several slaves, running on different logical cores.
|
|
|
|
|
|
2017-07-24 12:53:46 +05:30
|
|
|
* **Added NXP DPAA2 Eventdev PMD.**
|
|
|
|
|
|
|
|
|
|
Added the new dpaa2 eventdev driver for NXP DPAA2 devices. See the
|
|
|
|
|
"Event Device Drivers" document for more details on this new driver.
|
|
|
|
|
|
2017-07-04 10:22:56 +05:30
|
|
|
* **Added dpdk-test-eventdev test application.**
|
|
|
|
|
|
|
|
|
|
The dpdk-test-eventdev tool is a Data Plane Development Kit (DPDK) application
|
|
|
|
|
that allows exercising various eventdev use cases.
|
|
|
|
|
This application has a generic framework to add new eventdev based test cases
|
|
|
|
|
to verify functionality and measure the performance parameters of DPDK
|
|
|
|
|
eventdev devices.
|
|
|
|
|
|
2017-05-11 13:57:45 +01: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.
|
|
|
|
|
=========================================================
|
|
|
|
|
|
2017-08-03 15:53:50 +02:00
|
|
|
* **Starting with version 17.08, libnuma is required to build DPDK.**
|
|
|
|
|
|
2017-05-11 13:57:45 +01: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 ``rte_function_names`` or ``rte_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.
|
|
|
|
|
=========================================================
|
|
|
|
|
|
2017-07-12 10:25:01 +01:00
|
|
|
* **Modified the _rte_eth_dev_callback_process function in the ethdev library.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
The function ``_rte_eth_dev_callback_process()`` has been modified. The
|
|
|
|
|
return value has been changed from void to int and an extra parameter ``void
|
|
|
|
|
*ret_param`` has been added.
|
2017-07-12 10:25:01 +01:00
|
|
|
|
2017-07-10 12:39:49 +01:00
|
|
|
* **Moved bypass functions from the rte_ethdev library to ixgbe PMD**
|
|
|
|
|
|
|
|
|
|
* The following rte_ethdev library functions were removed:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* ``rte_eth_dev_bypass_event_show()``
|
|
|
|
|
* ``rte_eth_dev_bypass_event_store()``
|
|
|
|
|
* ``rte_eth_dev_bypass_init()``
|
|
|
|
|
* ``rte_eth_dev_bypass_state_set()``
|
|
|
|
|
* ``rte_eth_dev_bypass_state_show()``
|
|
|
|
|
* ``rte_eth_dev_bypass_ver_show()``
|
|
|
|
|
* ``rte_eth_dev_bypass_wd_reset()``
|
|
|
|
|
* ``rte_eth_dev_bypass_wd_timeout_show()``
|
|
|
|
|
* ``rte_eth_dev_wd_timeout_store()``
|
2017-07-10 12:39:49 +01:00
|
|
|
|
|
|
|
|
* The following ixgbe PMD functions were added:
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* ``rte_pmd_ixgbe_bypass_event_show()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_event_store()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_init()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_state_set()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_state_show()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_ver_show()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_wd_reset()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_wd_timeout_show()``
|
|
|
|
|
* ``rte_pmd_ixgbe_bypass_wd_timeout_store()``
|
2017-07-10 12:39:49 +01:00
|
|
|
|
2017-06-30 15:34:21 +01:00
|
|
|
* **Reworked rte_cryptodev library.**
|
|
|
|
|
|
|
|
|
|
The rte_cryptodev library has been reworked and updated. The following changes
|
|
|
|
|
have been made to it:
|
|
|
|
|
|
|
|
|
|
* The crypto device type enumeration has been removed from cryptodev library.
|
|
|
|
|
* The function ``rte_crypto_count_devtype()`` has been removed, and replaced
|
|
|
|
|
by the new function ``rte_crypto_count_by_driver()``.
|
2017-05-22 15:54:30 +02:00
|
|
|
* Moved crypto device driver names definitions to the particular PMDs.
|
|
|
|
|
These names are not public anymore.
|
2017-08-04 15:20:12 +01:00
|
|
|
* The ``rte_cryptodev_configure()`` function does not create the session
|
|
|
|
|
mempool for the device anymore.
|
|
|
|
|
* The ``rte_cryptodev_queue_pair_attach_sym_session()`` and
|
2017-07-05 06:26:13 +01:00
|
|
|
``rte_cryptodev_queue_pair_dettach_sym_session()`` functions require
|
|
|
|
|
the new parameter ``device id``.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Parameters of ``rte_cryptodev_sym_session_create()`` were modified to
|
|
|
|
|
accept ``mempool``, instead of ``device id`` and ``rte_crypto_sym_xform``.
|
|
|
|
|
* Removed ``device id`` parameter from ``rte_cryptodev_sym_session_free()``.
|
|
|
|
|
* Added a new field ``session_pool`` to ``rte_cryptodev_queue_pair_setup()``.
|
|
|
|
|
* Removed ``aad_size`` parameter from
|
|
|
|
|
``rte_cryptodev_sym_capability_check_auth()``.
|
|
|
|
|
* Added ``iv_size`` parameter to
|
|
|
|
|
``rte_cryptodev_sym_capability_check_auth()``.
|
|
|
|
|
* Removed ``RTE_CRYPTO_OP_STATUS_ENQUEUED`` from enum
|
|
|
|
|
``rte_crypto_op_status``.
|
2017-06-30 15:34:21 +01:00
|
|
|
|
2017-05-11 13:57:45 +01: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 ``rte_function_names`` or ``rte_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.
|
|
|
|
|
=========================================================
|
|
|
|
|
|
2017-08-08 16:26:00 +02:00
|
|
|
* Changed type of ``domain`` field in ``rte_pci_addr`` to ``uint32_t``
|
|
|
|
|
to follow the PCI standard.
|
|
|
|
|
|
|
|
|
|
* Added new ``rte_bus`` experimental APIs available as operators within the
|
|
|
|
|
``rte_bus`` structure.
|
|
|
|
|
|
|
|
|
|
* Made ``rte_devargs`` structure internal device representation generic to
|
|
|
|
|
prepare for a bus-agnostic EAL.
|
|
|
|
|
|
2017-07-02 06:41:02 +01:00
|
|
|
* **Reorganized the crypto operation structures.**
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
Some fields have been modified in the ``rte_crypto_op`` and
|
|
|
|
|
``rte_crypto_sym_op`` structures, as described in the `New Features`_
|
|
|
|
|
section.
|
2017-05-11 13:57:45 +01:00
|
|
|
|
2017-07-05 06:26:14 +01:00
|
|
|
* **Reorganized the crypto symmetric session structure.**
|
|
|
|
|
|
|
|
|
|
Some fields have been modified in the ``rte_cryptodev_sym_session``
|
|
|
|
|
structure, as described in the `New Features`_ section.
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Reorganized the rte_crypto_sym_cipher_xform structure.**
|
2017-07-02 06:41:14 +01:00
|
|
|
|
|
|
|
|
* Added cipher IV length and offset parameters.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Changed field size of key length from ``size_t`` to ``uint16_t``.
|
2017-07-02 06:41:14 +01:00
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* **Reorganized the rte_crypto_sym_auth_xform structure.**
|
2017-07-02 06:41:15 +01:00
|
|
|
|
|
|
|
|
* Added authentication IV length and offset parameters.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Changed field size of AAD length from ``uint32_t`` to ``uint16_t``.
|
|
|
|
|
* Changed field size of digest length from ``uint32_t`` to ``uint16_t``.
|
2017-07-02 06:41:27 +01:00
|
|
|
* Removed AAD length.
|
2017-08-04 15:20:12 +01:00
|
|
|
* Changed field size of key length from ``size_t`` to ``uint16_t``.
|
2017-07-02 06:41:15 +01:00
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* Replaced ``dev_type`` enumeration with ``uint8_t`` ``driver_id`` in
|
2017-07-05 06:26:14 +01:00
|
|
|
``rte_cryptodev_info`` and ``rte_cryptodev`` structures.
|
2017-06-30 15:34:21 +01:00
|
|
|
|
2017-07-05 06:26:12 +01:00
|
|
|
* Removed ``session_mp`` from ``rte_cryptodev_config``.
|
|
|
|
|
|
2017-05-11 13:57:45 +01:00
|
|
|
|
|
|
|
|
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_bitratestats.so.1
|
|
|
|
|
librte_cfgfile.so.2
|
|
|
|
|
librte_cmdline.so.2
|
2017-07-02 06:41:02 +01:00
|
|
|
+ librte_cryptodev.so.3
|
2017-05-11 13:57:45 +01:00
|
|
|
librte_distributor.so.1
|
2017-08-08 16:26:00 +02:00
|
|
|
+ librte_eal.so.5
|
2017-07-12 10:25:01 +01:00
|
|
|
+ librte_ethdev.so.7
|
2017-08-08 20:18:27 +05:30
|
|
|
+ librte_eventdev.so.2
|
lib/gro: add Generic Receive Offload API framework
Generic Receive Offload (GRO) is a widely used SW-based offloading
technique to reduce per-packet processing overhead. It gains
performance by reassembling small packets into large ones. This
patchset is to support GRO in DPDK. To support GRO, this patch
implements a GRO API framework.
To enable more flexibility to applications, DPDK GRO is implemented as
a user library. Applications explicitly use the GRO library to merge
small packets into large ones. DPDK GRO provides two reassembly modes.
One is called lightweight mode, the other is called heavyweight mode.
If applications want to merge packets in a simple way and the number
of packets is relatively small, they can use the lightweight mode.
If applications need more fine-grained controls, they can choose the
heavyweight mode.
rte_gro_reassemble_burst is the main reassembly API which is used in
lightweight mode and processes N packets at a time. For applications,
performing GRO in lightweight mode is simple. They just need to invoke
rte_gro_reassemble_burst. Applications can get GROed packets as soon as
rte_gro_reassemble_burst returns.
rte_gro_reassemble is the main reassembly API which is used in
heavyweight mode and tries to merge N inputted packets with the packets
in GRO reassembly tables. For applications, performing GRO in heavyweight
mode is relatively complicated. Before performing GRO, applications need
to create a GRO context object, which keeps reassembly tables of
desired GRO types, by rte_gro_ctx_create. Then applications can use
rte_gro_reassemble to merge packets. The GROed packets are in the
reassembly tables of the GRO context object. If applications want to get
them, applications need to manually flush them by flush API.
Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 13:46:44 +08:00
|
|
|
+ librte_gro.so.1
|
2017-05-11 13:57:45 +01:00
|
|
|
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.3
|
|
|
|
|
librte_mempool.so.2
|
|
|
|
|
librte_meter.so.1
|
|
|
|
|
librte_metrics.so.1
|
|
|
|
|
librte_net.so.1
|
|
|
|
|
librte_pdump.so.1
|
|
|
|
|
librte_pipeline.so.3
|
|
|
|
|
librte_pmd_bond.so.1
|
|
|
|
|
librte_pmd_ring.so.2
|
|
|
|
|
librte_port.so.3
|
|
|
|
|
librte_power.so.1
|
|
|
|
|
librte_reorder.so.1
|
|
|
|
|
librte_ring.so.1
|
|
|
|
|
librte_sched.so.1
|
|
|
|
|
librte_table.so.2
|
|
|
|
|
librte_timer.so.1
|
|
|
|
|
librte_vhost.so.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
=========================================================
|
2017-07-28 17:28:32 +03:00
|
|
|
|
|
|
|
|
* Intel(R) platforms with Mellanox(R) NICs combinations
|
|
|
|
|
|
|
|
|
|
* Platform details:
|
|
|
|
|
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2640 @ 2.50GHz
|
|
|
|
|
|
|
|
|
|
* OS:
|
|
|
|
|
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.3 (Maipo)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.2 (Maipo)
|
|
|
|
|
* Ubuntu 16.10
|
|
|
|
|
* Ubuntu 16.04
|
|
|
|
|
* Ubuntu 14.04
|
|
|
|
|
|
|
|
|
|
* MLNX_OFED: 4.1-1.0.2.0
|
|
|
|
|
|
|
|
|
|
* NICs:
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-3 Pro 40G MCX354A-FCC_Ax (2x40G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1007
|
|
|
|
|
* Firmware version: 2.40.5030
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 10G MCX4111A-XCAT (1x10G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 10G MCX4121A-XCAT (2x10G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 25G MCX4111A-ACAT (1x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 25G MCX4121A-ACAT (2x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 40G MCX4131A-BCAT/MCX413A-BCAT (1x40G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 40G MCX415A-BCAT (1x40G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 50G MCX4131A-GCAT/MCX413A-GCAT (1x50G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 50G MCX414A-BCAT (2x50G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
2017-08-04 15:20:12 +01:00
|
|
|
* Mellanox(R) ConnectX(R)-4 50G MCX415A-GCAT/MCX416A-BCAT/MCX416A-GCAT
|
|
|
|
|
(2x50G)
|
2017-07-28 17:28:32 +03:00
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 50G MCX415A-CCAT (1x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 100G MCX416A-CCAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1013
|
|
|
|
|
* Firmware version: 12.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 Lx 10G MCX4121A-XCAT (2x10G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1015
|
|
|
|
|
* Firmware version: 14.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-4 Lx 25G MCX4121A-ACAT (2x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1015
|
|
|
|
|
* Firmware version: 14.18.2000
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1017
|
|
|
|
|
* Firmware version: 16.19.1200
|
|
|
|
|
|
|
|
|
|
* Mellanox(R) ConnectX-5 Ex EN 100G MCX516A-CDAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x16
|
|
|
|
|
* Device ID: 15b3:1019
|
|
|
|
|
* Firmware version: 16.19.1200
|
2017-07-31 12:30:29 +08:00
|
|
|
|
|
|
|
|
* Intel(R) platforms with Intel(R) NICs combinations
|
|
|
|
|
|
|
|
|
|
* CPU
|
|
|
|
|
|
|
|
|
|
* Intel(R) Atom(TM) CPU C2758 @ 2.40GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU D-1540 @ 2.00GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-4667 v3 @ 2.00GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2658 v2 @ 2.40GHz
|
|
|
|
|
* Intel(R) Xeon(R) CPU E5-2658 v3 @ 2.20GHz
|
|
|
|
|
|
|
|
|
|
* OS:
|
|
|
|
|
|
|
|
|
|
* CentOS 7.2
|
|
|
|
|
* Fedora 25
|
|
|
|
|
* FreeBSD 11
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.3
|
|
|
|
|
* SUSE Enterprise Linux 12
|
|
|
|
|
* Wind River Linux 8
|
|
|
|
|
* Ubuntu 16.04
|
|
|
|
|
* Ubuntu 16.10
|
|
|
|
|
|
|
|
|
|
* NICs:
|
|
|
|
|
|
|
|
|
|
* Intel(R) 82599ES 10 Gigabit Ethernet Controller
|
|
|
|
|
|
|
|
|
|
* Firmware version: 0x61bf0001
|
|
|
|
|
* Device id (pf/vf): 8086:10fb / 8086:10ed
|
|
|
|
|
* Driver version: 4.0.1-k (ixgbe)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Corporation Ethernet Connection X552/X557-AT 10GBASE-T
|
|
|
|
|
|
|
|
|
|
* Firmware version: 0x800001cf
|
|
|
|
|
* Device id (pf/vf): 8086:15ad / 8086:15a8
|
|
|
|
|
* Driver version: 4.2.5 (ixgbe)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Ethernet Converged Network Adapter X710-DA4 (4x10G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.01 0x80003205
|
|
|
|
|
* Device id (pf/vf): 8086:1572 / 8086:154c
|
|
|
|
|
* Driver version: 2.0.19 (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Ethernet Converged Network Adapter X710-DA2 (2x10G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.01 0x80003204
|
|
|
|
|
* Device id (pf/vf): 8086:1572 / 8086:154c
|
|
|
|
|
* Driver version: 2.0.19 (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Ethernet Converged Network Adapter XXV710-DA2 (2x25G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.01 0x80003221
|
|
|
|
|
* Device id (pf/vf): 8086:158b
|
|
|
|
|
* Driver version: 2.0.19 (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Ethernet Converged Network Adapter XL710-QDA2 (2X40G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.01 0x8000321c
|
|
|
|
|
* Device id (pf/vf): 8086:1583 / 8086:154c
|
|
|
|
|
* Driver version: 2.0.19 (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel(R) Corporation I350 Gigabit Network Connection
|
|
|
|
|
|
|
|
|
|
* Firmware version: 1.48, 0x800006e7
|
|
|
|
|
* Device id (pf/vf): 8086:1521 / 8086:1520
|
|
|
|
|
* Driver version: 5.2.13-k (igb)
|
