From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
To: dev@dpdk.org
Cc: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] doc: add vxlan and nvgre tunnel update in release notes
Date: Mon, 28 May 2018 17:12:22 +0100 [thread overview]
Message-ID: <20180528161222.18935-2-mohammad.abdul.awal@intel.com> (raw)
In-Reply-To: <20180528161222.18935-1-mohammad.abdul.awal@intel.com>
Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
---
doc/guides/rel_notes/release_18_05.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index 511d51908..37d102572 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -323,6 +323,15 @@ New Features
spawned on an as needed basis through configuration parameters passed to the
driver of the underlying device using devargs.
+* **Added support for VXLAN and NVGRE tunnel endpoint.**
+
+ New actions types have been added to support encapsulation and decapsulation
+ operations for a tunnel endpoint. The new action types are
+ RTE_FLOW_ACTION_TYPE_[VXLAN/NVGRE]_ENCAP, RTE_FLOW_ACTION_TYPE_[VXLAN/NVGRE]_DECAP,
+ RTE_FLOW_ACTION_TYPE_JUMP. New item type RTE_FLOW_ACTION_TYPE_MARK has been
+ added to match a flow against a previously marked flow. It also introduced shared
+ counter to flow API to counte for a group of flows.
+
API Changes
-----------
@@ -457,6 +466,14 @@ API Changes
redirect matching traffic to a specific physical port.
* PORT_ID pattern item and actions were added to match and target DPDK
port IDs at a higher level than PHY_PORT.
+ * RTE_FLOW_ACTION_TYPE_[VXLAN/NVGRE]_ENCAP action items were added to support
+ tunnel encapsulation operation for VXLAN and NVGRE type tunnel endpoint.
+ * RTE_FLOW_ACTION_TYPE_[VXLAN/NVGRE]_DECAP action items were added to support
+ tunnel decapsulation operation for VXLAN and NVGRE type tunnel endpoint.
+ * RTE_FLOW_ACTION_TYPE_JUMP action item was added to support a matched flow
+ to be redirected to the specific group.
+ * RTE_FLOW_ACTION_TYPE_MARK item type has been added to match a flow against
+ a previously marked flow.
* ethdev: change flow APIs regarding count action:
* ``rte_flow_create()`` API count action now requires the ``struct rte_flow_action_count``.
--
2.17.0
next prev parent reply other threads:[~2018-05-28 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 16:12 [dpdk-dev] [PATCH 1/2] doc: add port representor " Mohammad Abdul Awal
2018-05-28 16:12 ` Mohammad Abdul Awal [this message]
2018-05-28 16:52 ` [dpdk-dev] [PATCH 2/2] doc: add vxlan and nvgre tunnel " Mcnamara, John
2018-05-29 10:31 ` Thomas Monjalon
2018-05-28 16:52 ` [dpdk-dev] [PATCH 1/2] doc: add port representor " Mcnamara, John
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 16:08 Mohammad Abdul Awal
2018-05-28 16:08 ` [dpdk-dev] [PATCH 2/2] doc: add vxlan and nvgre tunnel " Mohammad Abdul Awal
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=20180528161222.18935-2-mohammad.abdul.awal@intel.com \
--to=mohammad.abdul.awal@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).