From: Jasvinder Singh <jasvinder.singh@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: update release notes for ip_pipeline app
Date: Wed, 4 Nov 2015 15:04:49 +0000 [thread overview]
Message-ID: <1446649489-11990-1-git-send-email-jasvinder.singh@intel.com> (raw)
This patch updates the release notes with the features
added to ip_pipeline application.
Signed-off-by: Jasvinder Singh <jasvinder.singh@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
next reply other threads:[~2015-11-04 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 15:04 Jasvinder Singh [this message]
2015-11-04 15:12 ` De Lara Guarch, Pablo
2015-11-04 15:28 ` Singh, Jasvinder
2015-11-04 17:03 ` [dpdk-dev] [PATCH v2] " Jasvinder Singh
2015-11-05 14:18 ` Zhang, Roy Fan
2015-12-13 23:11 ` Thomas Monjalon
2016-03-14 13:44 [dpdk-dev] [PATCH] " Jasvinder Singh
2016-03-16 20:35 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446649489-11990-1-git-send-email-jasvinder.singh@intel.com \
--to=jasvinder.singh@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).