From: Wang Ying A <ying.a.wang@intel.com>
To: qi.z.zhang@intel.com, adrien.mazarguil@6wind.com
Cc: xiaolong.ye@intel.com, qiming.yang@intel.com, dev@dpdk.org,
ying.a.wang@intel.com
Subject: [dpdk-dev] [PATCH v3 0/2] add GTP/PPPoE to flow API
Date: Tue, 20 Aug 2019 14:50:57 +0800 [thread overview]
Message-ID: <20190820065059.62140-1-ying.a.wang@intel.com> (raw)
In-Reply-To: <20190814032430.404190-1-ying.a.wang@intel.com>
patch 1/2: Add GTP extension header to flow API.
patch 2/2: Add PPPoE to flow API.
---
v3: Split original patch, one for GTP and the other for PPPoE.
Add RTE_FLOW_ITEM_TYPE_PPPOE_PROTO_ID for PPPoE session packets.
v2: Remove Gerrit Change-Id's.
---
Wang Ying A (2):
ethdev: add GTP extension header to flow API
ethdev: add PPPoE to flow API
app/test-pmd/cmdline_flow.c | 87 ++++++++++++++++++++++++++-
doc/guides/prog_guide/rte_flow.rst | 28 +++++++++
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 13 ++++
lib/librte_ethdev/rte_flow.c | 5 ++
lib/librte_ethdev/rte_flow.h | 93 +++++++++++++++++++++++++++++
5 files changed, 225 insertions(+), 1 deletion(-)
--
2.15.1
next prev parent reply other threads:[~2019-08-20 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 3:00 [dpdk-dev] [PATCH] ethdev: add more protocol support in " Wang Ying A
2019-08-14 3:24 ` [dpdk-dev] [PATCH v2] " Wang Ying A
2019-08-14 9:08 ` Adrien Mazarguil
2019-08-19 11:53 ` Zhang, Qi Z
2019-08-20 6:50 ` Wang Ying A [this message]
2019-08-20 6:50 ` [dpdk-dev] [PATCH v3 1/2] ethdev: add GTP extension header to " Wang Ying A
2019-08-28 6:00 ` [dpdk-dev] [PATCH v4 0/2] add GTP/PPPoE " Wang Ying A
2019-08-28 6:00 ` [dpdk-dev] [PATCH v4 1/2] ethdev: add GTP extension header " Wang Ying A
2019-09-28 19:02 ` Ori Kam
2019-08-28 6:00 ` [dpdk-dev] [PATCH v4 2/2] ethdev: add PPPoE " Wang Ying A
2019-09-28 19:05 ` Ori Kam
2019-09-23 23:44 ` [dpdk-dev] [PATCH v4 0/2] add GTP/PPPoE " Zhang, Qi Z
2019-10-01 7:52 ` Ferruh Yigit
2019-08-20 6:50 ` [dpdk-dev] [PATCH v3 2/2] ethdev: add PPPoE " Wang Ying A
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=20190820065059.62140-1-ying.a.wang@intel.com \
--to=ying.a.wang@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=xiaolong.ye@intel.com \
/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).