From: Shiri Kuzin <shirik@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
NBU-Contact-Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: [dpdk-dev] [RFC] ethdev: introduce GENEVE header extension item
Date: Sun, 16 Aug 2020 10:15:03 +0000 [thread overview]
Message-ID: <BYAPR12MB2597118FA6A2A8CEAD5B1306AA5E0@BYAPR12MB2597.namprd12.prod.outlook.com> (raw)
The Geneve tunneling protocol is designed to allow
the user to specify some data context on the packet.
The header extension options is the mean intended
to present the user data. These ones are implemented
in TLV (Type-Length-Value) fashion, in order to
support these Geneve protocol feature we will
introduce the new item "rte_flow_item_geneve_option"
The support for new item will be added to testpmd
and include values and masks for the fields:
- class
- type
- data length
- data itself
The usage example:
"flow create 0 ingress pattern ipv4 / udp /
geneve / geneve_opt class is 102 type is 80
type mask ff data is 10002 data mask is
7fffffff / end actions drop / end "
New item will be added to testpmd to support
raw encap/decap action.
Signed-off-by: Shiri Kuzin <shirik@nvidia.com>
---
lib/librte_ethdev/rte_flow.h | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
index da8bfa5..d04ee7c 100644
--- a/lib/librte_ethdev/rte_flow.h
+++ b/lib/librte_ethdev/rte_flow.h
@@ -347,6 +347,13 @@ enum rte_flow_item_type {
RTE_FLOW_ITEM_TYPE_GENEVE,
/**
+ * Matches a GENEVE Variable Length Option.
+ *
+ * See struct rte_flow_item_geneve_option.
+ */
+ RTE_FLOW_ITEM_TYPE_GENEVE_OPTION,
+
+ /**
* Matches a VXLAN-GPE header.
*
* See struct rte_flow_item_vxlan_gpe.
@@ -1097,6 +1104,24 @@ struct rte_flow_item_geneve {
#endif
/**
+ * RTE_FLOW_ITEM_TYPE_GENEVE_OPTION.
+ *
+ * Matches a GENEVE Variable Length Option
+ */
+struct rte_flow_item_geneve_option {
+ rte_be16_t option_class;
+ uint8_t option_type;
+#if RTE_BYTE_ORDER == RTE_LITTLE_ENDIAN
+ uint8_t length:5;
+ uint8_t rsvd0:3;
+#else
+ uint8_t rsvd0:3;
+ uint8_t length:5;
+#endif
+ uint8_t data[];
+};
+
+/**
* RTE_FLOW_ITEM_TYPE_VXLAN_GPE (draft-ietf-nvo3-vxlan-gpe-05).
*
* Matches a VXLAN-GPE header.
--
1.8.3.1
next reply other threads:[~2020-08-16 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 10:15 Shiri Kuzin [this message]
2020-08-16 17:25 ` Stephen Hemminger
2020-08-17 6:36 ` Shiri Kuzin
2020-09-15 7:59 ` Ori Kam
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=BYAPR12MB2597118FA6A2A8CEAD5B1306AA5E0@BYAPR12MB2597.namprd12.prod.outlook.com \
--to=shirik@nvidia.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.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).