From: Shiri Kuzin <shirik@nvidia.com>
To: dev@dpdk.org
Cc: viacheslavo@nvidia.com, adrien.mazarguil@6wind.com, rasland@nvidia.com
Subject: [dpdk-dev] [RFC v3 0/8] ethdev: introduce GENEVE header TLV option item
Date: Wed, 16 Dec 2020 15:02:07 +0200 [thread overview]
Message-ID: <1608123735-3662-1-git-send-email-shirik@nvidia.com> (raw)
In-Reply-To: <1599118768-13265-1-git-send-email-shirik@nvidia.com>
The Geneve tunneling protocol is designed to allow the
user to specify some data context on the packet.
The GENEVE TLV (Type-Length-Variable) Option
is the mean intended to present the user data.
In order to support GENEVE TLV Option the new rte_flow
item "rte_flow_item_geneve_opt" is introduced.
The new item contains the values and masks for the
following fields:
-option class
-option type
-length
-data
The usage example:
"flow create 0 ingress pattern eth / ipv4 / udp / geneve vni is 100 /
geneve-opt class is 5 length is 1 type is 0 data is 0x66998800 /
end actions count / drop / end"
New item will be added to testpmd to support
raw encap/decap action.
Shiri Kuzin (7):
lib/librte_ethdev: introduce GENEVE header TLV option item
common/mlx5: check GENEVE TLV support in HCA attributes
common/mlx5: create GENEVE TLV option object with DevX
net/mlx5: create GENEVE TLV option management
net/mlx5: add GENEVE TLV option flow validation
net/mlx5: add GENEVE TLV option flow translation
doc: update GENEVE TLV option support
Viacheslav Ovsiienko (1):
app/testpmd: add GENEVE option item support
app/test-pmd/cmdline_flow.c | 102 ++++++++++++++-
doc/guides/nics/mlx5.rst | 18 ++-
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 8 ++
drivers/common/mlx5/mlx5_devx_cmds.c | 61 +++++++++
drivers/common/mlx5/mlx5_devx_cmds.h | 9 ++
drivers/common/mlx5/mlx5_prm.h | 28 ++++-
drivers/common/mlx5/version.map | 1 +
drivers/net/mlx5/mlx5.c | 2 +
drivers/net/mlx5/mlx5.h | 13 ++
drivers/net/mlx5/mlx5_flow.c | 120 ++++++++++++++++++
drivers/net/mlx5/mlx5_flow.h | 11 ++
drivers/net/mlx5/mlx5_flow_dv.c | 188 +++++++++++++++++++++++++++-
lib/librte_ethdev/rte_flow.c | 1 +
lib/librte_ethdev/rte_flow.h | 33 +++++
14 files changed, 584 insertions(+), 11 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2020-12-16 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 7:39 [dpdk-dev] [RFC v2] ethdev: introduce GENEVE header extension item Shiri Kuzin
2020-10-01 16:25 ` Ferruh Yigit
2020-10-05 12:44 ` Shiri Kuzin
2020-10-05 13:10 ` Ferruh Yigit
2020-12-16 13:02 ` Shiri Kuzin [this message]
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 1/8] lib/librte_ethdev: introduce GENEVE header TLV option item Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 2/8] app/testpmd: add GENEVE option item support Shiri Kuzin
2021-01-14 20:08 ` Ajit Khaparde
2021-01-17 8:31 ` Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 3/8] common/mlx5: check GENEVE TLV support in HCA attributes Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 4/8] common/mlx5: create GENEVE TLV option object with DevX Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 5/8] net/mlx5: create GENEVE TLV option management Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 6/8] net/mlx5: add GENEVE TLV option flow validation Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 7/8] net/mlx5: add GENEVE TLV option flow translation Shiri Kuzin
2020-12-16 13:02 ` [dpdk-dev] [RFC v3 8/8] doc: update GENEVE TLV option support Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 0/6] add GTP PSC extension header support Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 1/6] ethdev: update GTP headers Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 2/6] app/testpmd: add GTP PSC option support in raw sets Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 3/6] common/mlx5: add matcher fields for GTP extensions Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 4/6] net/mlx5: add GTP PSC flow validation Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 5/6] net/mlx5: add GTP PSC item translation Shiri Kuzin
2020-12-16 14:25 ` [dpdk-dev] [RFC 6/6] doc: update GTP extension header support Shiri Kuzin
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=1608123735-3662-1-git-send-email-shirik@nvidia.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).