From patchwork Wed Nov 4 15:04:49 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jasvinder Singh X-Patchwork-Id: 8677 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 8607B8E9F; Wed, 4 Nov 2015 16:06:05 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 862BF8DAC for ; Wed, 4 Nov 2015 16:06:03 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP; 04 Nov 2015 07:05:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,243,1444719600"; d="scan'208";a="811622041" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga001.jf.intel.com with ESMTP; 04 Nov 2015 07:04:55 -0800 Received: from sivswdev02.ir.intel.com (sivswdev02.ir.intel.com [10.237.217.46]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id tA4F4nHK030471; Wed, 4 Nov 2015 15:04:49 GMT Received: from sivswdev02.ir.intel.com (localhost [127.0.0.1]) by sivswdev02.ir.intel.com with ESMTP id tA4F4nvE012098; Wed, 4 Nov 2015 15:04:49 GMT Received: (from jasvinde@localhost) by sivswdev02.ir.intel.com with id tA4F4nTi012094; Wed, 4 Nov 2015 15:04:49 GMT From: Jasvinder Singh To: dev@dpdk.org Date: Wed, 4 Nov 2015 15:04:49 +0000 Message-Id: <1446649489-11990-1-git-send-email-jasvinder.singh@intel.com> X-Mailer: git-send-email 1.7.4.1 Subject: [dpdk-dev] [PATCH] doc: update release notes for ip_pipeline app X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" This patch updates the release notes with the features added to ip_pipeline application. Signed-off-by: Jasvinder Singh --- 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 ~~~~~