From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
"Yuying Zhang" <yuying.zhang@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
"Thomas Monjalon" <thomas@monjalon.net>
Subject: [RFC 0/2] ethdev: extend modify field API
Date: Thu, 20 Apr 2023 12:21:43 +0300 [thread overview]
Message-ID: <20230420092145.522389-1-michaelba@nvidia.com> (raw)
This petch-set extend the modify field action API to support 2 special
cases.
1. Modify field when the relevant header appears multiple times inside
same encapsulation level.
2. Modify Geneve option header which is specified by its "type" and
"class" fields.
In current API, the header type is provided by "rte_flow_field_id"
enumeration and the encapsulation level (inner/outer/tunnel) is
specified by "data.level" field.
However, there is no way to specify header inside encapsulation level.
For example, for this packet:
eth / mpls / mpls / mpls / ipv4 / udp
the both second and third MPLS headers cannot be modified using this
API.
Michael Baum (2):
ethdev: add GENEVE TLV option modification support
ethdev: add MPLS header modification support
app/test-pmd/cmdline_flow.c | 69 +++++++++++++++++++++++++++-
doc/guides/prog_guide/rte_flow.rst | 33 +++++++++++---
lib/ethdev/rte_flow.h | 72 ++++++++++++++++++++++++++++--
3 files changed, 165 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-20 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 9:21 Michael Baum [this message]
2023-04-20 9:21 ` [RFC 1/2] ethdev: add GENEVE TLV option modification support Michael Baum
2023-04-20 9:21 ` [RFC 2/2] ethdev: add MPLS header " Michael Baum
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=20230420092145.522389-1-michaelba@nvidia.com \
--to=michaelba@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@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).