From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Michael Baum <michaelba@nvidia.com>, dev@dpdk.org
Cc: Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v5 0/5] ethdev: modify field API for multiple headers
Date: Thu, 1 Jun 2023 12:54:27 +0100 [thread overview]
Message-ID: <00fef70e-7d3b-5aa1-a882-e4e9303f2ca0@amd.com> (raw)
In-Reply-To: <20230523213157.3905696-1-michaelba@nvidia.com>
On 5/23/2023 10:31 PM, Michael Baum wrote:
> This patch-set extend the modify field action API to support both
> multiple MPLS and GENEVE option headers.
>
> 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.
>
> RFC:
> https://patchwork.dpdk.org/project/dpdk/cover/20230420092145.522389-1-michaelba@nvidia.com/
>
> v2:
> - Change "sub_level" name to "tag_index".
> - Squash PMD changes into API changes patch.
> - Remove PMD private patch from the patch-set.
>
> v3:
> - Add TAG array API change to release notes.
> - Improve comment and documentation.
>
> v4:
> - Add "Acked-by" labels.
> - Add PMD adjustment for TAG array API change.
>
> v5:
> - Fix location of level validation.
>
> Michael Baum (5):
> doc: fix blank lines in modify field action description
> doc: fix blank line in asynchronous operations description
> doc: fix wrong indentation in RSS action description
> ethdev: add GENEVE TLV option modification support
> ethdev: add MPLS header modification support
>
Doc patches merged into single one,
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-01 11:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 6:37 [PATCH v1 0/7] " Michael Baum
2023-05-16 6:37 ` [PATCH v1 1/7] doc: fix blank lines in modify field action description Michael Baum
2023-05-16 6:37 ` [PATCH v1 2/7] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-17 17:13 ` Ori Kam
2023-05-16 6:37 ` [PATCH v1 3/7] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-18 6:18 ` Ori Kam
2023-05-16 6:37 ` [PATCH v1 4/7] net/mlx5: reduce modify field encapsulation level size Michael Baum
2023-05-16 6:37 ` [PATCH v1 5/7] ethdev: add GENEVE TLV option modification support Michael Baum
2023-05-16 6:37 ` [PATCH v1 6/7] ethdev: add MPLS header " Michael Baum
2023-05-16 6:37 ` [PATCH v1 7/7] net/mlx5: add MPLS modify field support Michael Baum
2023-05-18 17:40 ` [PATCH v2 0/5] ethdev: modify field API for multiple headers Michael Baum
2023-05-18 17:40 ` [PATCH v2 1/5] doc: fix blank lines in modify field action description Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-21 10:08 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 4/5] ethdev: add GENEVE TLV option modification support Michael Baum
2023-05-21 18:52 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 5/5] ethdev: add MPLS header " Michael Baum
2023-05-21 19:03 ` Ori Kam
2023-05-22 12:04 ` Michael Baum
2023-05-22 19:27 ` [PATCH v3 0/5] ethdev: modify field API for multiple headers Michael Baum
2023-05-22 19:28 ` [PATCH v3 1/5] doc: fix blank lines in modify field action description Michael Baum
2023-05-22 19:28 ` [PATCH v3 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-22 19:28 ` [PATCH v3 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-22 19:28 ` [PATCH v3 4/5] ethdev: add GENEVE TLV option modification support Michael Baum
2023-05-22 19:28 ` [PATCH v3 5/5] ethdev: add MPLS header " Michael Baum
2023-05-23 10:40 ` [PATCH v3 0/5] ethdev: modify field API for multiple headers Ori Kam
2023-05-23 12:48 ` [PATCH v4 " Michael Baum
2023-05-23 12:48 ` [PATCH v4 1/5] doc: fix blank lines in modify field action description Michael Baum
2023-05-23 12:48 ` [PATCH v4 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-23 12:48 ` [PATCH v4 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-23 12:48 ` [PATCH v4 4/5] ethdev: add GENEVE TLV option modification support Michael Baum
2023-05-23 12:48 ` [PATCH v4 5/5] ethdev: add MPLS header " Michael Baum
2023-05-23 21:31 ` [PATCH v5 0/5] ethdev: modify field API for multiple headers Michael Baum
2023-05-23 21:31 ` [PATCH v5 1/5] doc: fix blank lines in modify field action description Michael Baum
2023-05-23 21:31 ` [PATCH v5 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-23 21:31 ` [PATCH v5 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-23 21:31 ` [PATCH v5 4/5] ethdev: add GENEVE TLV option modification support Michael Baum
2023-05-23 21:31 ` [PATCH v5 5/5] ethdev: add MPLS header " Michael Baum
2023-06-01 11:54 ` Ferruh Yigit
2023-06-01 11:54 ` Ferruh Yigit [this message]
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=00fef70e-7d3b-5aa1-a882-e4e9303f2ca0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=michaelba@nvidia.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).