From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
To: dev@dpdk.org, bernard.iremonger@intel.com, adrien.mazarguil@6wind.com
Subject: [dpdk-dev] [PATCH v2 0/2] Added vxlan/nvgre encap/decap support to testpmd
Date: Fri, 11 May 2018 18:13:59 +0100 [thread overview]
Message-ID: <1526058841-31650-1-git-send-email-mohammad.abdul.awal@intel.com> (raw)
Changes in v2:
* Added documentation in testpmd user guide.
* Added vlan header for vxlan/nvgre encap.
* Fixed other comments.
In this patch set we have enabled testpmd application with ability to create
a flow with vxlan/nvgre tunnel types and with encapsulation/decapsulation
functionalities.
We have also updated the testpmd user guide documentation with how to used new
action types RTE_FLOW_ACTION_VXLAN_ENCAP, RTE_FLOW_ACTION_VXLAN_DECAP,
RTE_FLOW_ACTION_NVGRE_ENCAP, RTE_FLOW_ACTION_NVGRE_DECAP capabilities.
Mohammad Abdul Awal (2):
app/testpmd: enabled vxlan and nvgre encap/decap support for rte_flow
doc/guides: updated testpmd app user guide for vxlan/nvgre encap/decap
app/test-pmd/cmdline_flow.c | 937 ++++++++++++++++++++++++++++
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 50 ++
2 files changed, 987 insertions(+)
--
2.7.4
next reply other threads:[~2018-05-11 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 17:13 Mohammad Abdul Awal [this message]
2018-05-11 17:14 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: enabled vxlan and nvgre encap/decap support for rte_flow Mohammad Abdul Awal
2018-05-14 11:14 ` Iremonger, Bernard
2018-05-11 17:14 ` [dpdk-dev] [PATCH v2 2/2] doc/guides: updated testpmd app user guide for vxlan/nvgre encap/decap Mohammad Abdul Awal
2018-05-14 10:35 ` Iremonger, Bernard
2018-05-14 15:42 ` Mohammad Abdul Awal
2018-06-14 17:14 ` Ferruh Yigit
2018-06-14 17:19 ` Ferruh Yigit
2018-06-18 11:20 ` 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=1526058841-31650-1-git-send-email-mohammad.abdul.awal@intel.com \
--to=mohammad.abdul.awal@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@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).