DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ori Kam <orika@nvidia.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
	Chaoyong He <chaoyong.he@corigine.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Deprecated packet modification flow actions
Date: Fri, 8 Mar 2024 16:17:05 +0000	[thread overview]
Message-ID: <PH0PR12MB8800E27FFA7BDEAF83808EF6A4272@PH0PR12MB8800.namprd12.prod.outlook.com> (raw)

Hi all,

I would like to start a discussion about legacy flow actions for packet modification.
As of DPDK 21.11 many packet modification flow actions were deprecated in favor of generic
RTE_FLOW_ACTION_TYPE_MODIFY_FIELD action (see [1]).
I compiled a review of the current state of all deprecated actions along with changes since 21.11:

RTE_FLOW_ACTION_TYPE_OF_SET_MPLS_TTL    removed in 22.11
RTE_FLOW_ACTION_TYPE_OF_DEC_MPLS_TTL    removed in 22.11
RTE_FLOW_ACTION_TYPE_OF_SET_NW_TTL      removed in 22.11
RTE_FLOW_ACTION_TYPE_OF_DEC_NW_TTL      bnxt*, sfc
RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_OUT    removed in 22.11
RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_IN     removed in 22.11
RTE_FLOW_ACTION_TYPE_SET_IPV4_SRC       bnxt, cxgbe, mlx5, nfp (from 22.11), sfc (from 23.07)
RTE_FLOW_ACTION_TYPE_SET_IPV4_DST       bnxt, cxgbe, mlx5, nfp (from 22.11), sfc (from 23.07)
RTE_FLOW_ACTION_TYPE_SET_IPV6_SRC       bnxt*, cxgbe, mlx5, nfp (from 22.11)
RTE_FLOW_ACTION_TYPE_SET_IPV6_DST       bnxt*, cxgbe, mlx5, nfp (from 22.11)
RTE_FLOW_ACTION_TYPE_SET_TP_SRC         bnxt, cxgbe, mlx5, nfp (from 22.11), sfc (from 23.07)
RTE_FLOW_ACTION_TYPE_SET_TP_DST         bnxt, cxgbe, mlx5, nfp (from 22.11), sfc (from 23.07)
RTE_FLOW_ACTION_TYPE_DEC_TTL            bnxt, mlx5, sfc
RTE_FLOW_ACTION_TYPE_SET_TTL            bnxt*, mlx5, nfp (from 22.11)
RTE_FLOW_ACTION_TYPE_SET_MAC_SRC        bnxt, cxgbe, mlx5, nfp (from 22.11), sfc
RTE_FLOW_ACTION_TYPE_SET_MAC_DST        bnxt, cxgbe, mlx5, nfp (from 22.11), sfc
RTE_FLOW_ACTION_TYPE_INC_TCP_SEQ        bnxt*, mlx5
RTE_FLOW_ACTION_TYPE_DEC_TCP_SEQ        bnxt*, mlx5
RTE_FLOW_ACTION_TYPE_INC_TCP_ACK        bnxt*, mlx5
RTE_FLOW_ACTION_TYPE_DEC_TCP_ACK        bnxt*, mlx5
RTE_FLOW_ACTION_TYPE_SET_IPV4_DSCP      mlx5, nfp (from 22.11)
RTE_FLOW_ACTION_TYPE_SET_IPV6_DSCP      mlx5, nfp (from 22.11)
RTE_FLOW_ACTION_TYPE_SET_TAG            mlx5
RTE_FLOW_ACTION_TYPE_SET_META           mlx5

bnxt* - Based on my analysis, this action type is used only to reject unsupported actions.

RTE_FLOW_ACTION_TYPE_MODIFY_FIELD flow action itself is supported only by mlx5 PMD.

Question to ethdev and flow API maintainers, and to technical board:

As of now, MODIFY_FIELD action support in mlx5 PMD covers all deprecated modify actions.
Legacy flow actions can be removed from mlx5 PMD.
What in your opinion would be an appropriate timeline for removing them? Should we wait until 24.11 LTS release?

Question to driver maintainers:

Do you have plans to add support for RTE_FLOW_ACTION_TYPE_MODIFY_FIELD flow action in future releases?

[1]: commit bef7c9ff285a ("ethdev: announce migration to generic flow modify action")

Best regards,
Dariusz Sosnowski

             reply	other threads:[~2024-03-08 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 16:17 Dariusz Sosnowski [this message]
2024-03-11  1:42 ` Chaoyong He
2024-03-15  9:24   ` Dariusz Sosnowski
2024-03-15 13:34     ` Kevin Traynor

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=PH0PR12MB8800E27FFA7BDEAF83808EF6A4272@PH0PR12MB8800.namprd12.prod.outlook.com \
    --to=dsosnowski@nvidia.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=orika@nvidia.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).