This patch updates the release notes with the features added to ip_pipeline application.
Signed-off-by: Jasvinder Singh <jasvinder.singh at intel.com> --- doc/guides/rel_notes/release_2_2.rst | 49 ++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst index 0c7abe9..2245126 100644 --- a/doc/guides/rel_notes/release_2_2.rst +++ b/doc/guides/rel_notes/release_2_2.rst @@ -176,6 +176,55 @@ Libraries Examples ~~~~~~~~ +* **IP-Pipeline Application.** + + The following features have been added to ip_pipeline + application; + + * Added Multiple Producers Multiple Consumers (MPSC) + and fragmentation/reassembly support to software rings. + + * Added dynamic pipeline reconfiguration feature that + allows binding pipeline to other threads at runtime + using CLI commands. + + * Added Enable/disable of promisc mode from ip_pipeline + configuration file. + + * Added check on rx queues and tx queues of each link + whether they are used correctly in ip_pipeline + configuration file. + + * Added flow id parameters to the flow-classification + table entries. + + * Added more functions to the routing pipeline, for examples, + Fast-path ARP table enable/disable, Double-tagged VLAN + (Q-in-Q) packet enacapsulation for the next-hop, MPLS + encapsulation for the next-hop, Add colour (Traffic-class + for QoS) to the MPLS tag, Classification action to select + the input queue of the hierarchical scehdular (QoS). + All these functions can be enabled or disabled thorugh + congifuration file. + + * Added flow-actions pipeline to ip_pipeline application. + Some of the operations of flow classification pipeline + such as traffic metering/marking (for e.g. Two Rate Three + Color Marker (trTCM)), policer can be performed separately + in flow-actions pipeline to avoid excessive computational + burden on the CPU core running the flow-classification + pipeline. + + * Modified the passthrough pipeline's actions-handler to + implement a generic approach to extract fields from the + packet's header and copying them to packet metadata. The + fields are selected at the desired offset on the basis + of the mask specified in application configuration file. + The extracted fields, for instance, can be used to compute + hash for the lookup table. This feature exposes more + flexibility to the users as they will be able to employ + new protocol headers and specify the required fields to be + extracted. Other ~~~~~ -- 2.4.3
