From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH v3] ethdev: deprecate header fields and metadata flow actions
Date: Thu, 25 Nov 2021 14:13:28 +0000 [thread overview]
Message-ID: <DM6PR12MB3753CE024A99B824C19559BCDF629@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1989679.70EXCg8c8L@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, November 25, 2021 15:07
> To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>; Ajit Khaparde
> <ajit.khaparde@broadcom.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Rahul Lakkireddy
> <rahul.lakkireddy@chelsio.com>; Slava Ovsiienko <viacheslavo@nvidia.com>;
> Ferruh Yigit <ferruh.yigit@intel.com>
> Cc: dev@dpdk.org; Ori Kam <orika@nvidia.com>
> Subject: Re: [PATCH v3] ethdev: deprecate header fields and metadata flow
> actions
>
> 25/11/2021 12:53, Ferruh Yigit:
> > On 11/24/2021 3:37 PM, Viacheslav Ovsiienko wrote:
> > > The generic RTE_FLOW_ACTION_TYPE_MODIFY_FIELD action was
> introduced
> > > by [1]. This action provides an unified way to perform various
> > > arithmetic and transfer operations over packet network header fields
> > > and packet metadata.
> > >
> > > [1] commit 641dbe4fb053 ("net/mlx5: support modify field flow
> > > action")
> > >
> > > On other side there are a bunch of multiple legacy actions, that can
> > > be superseded by the generic modify field action:
> > >
> > > RTE_FLOW_ACTION_TYPE_OF_SET_MPLS_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_DEC_MPLS_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_SET_NW_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_DEC_NW_TTL sfc
> > > RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_OUT
> > > RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_IN
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_SRC bnxt, cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_DST bnxt, cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_SRC cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_DST cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_TP_SRC cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_TP_DST cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_DEC_TTL mlx5, sfc
> > > RTE_FLOW_ACTION_TYPE_SET_TTL mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_MAC_SRC cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_MAC_DST cxgbe, mlx5
> > > RTE_FLOW_ACTION_TYPE_INC_TCP_SEQ mlx5
> > > RTE_FLOW_ACTION_TYPE_DEC_TCP_SEQ mlx5
> > > RTE_FLOW_ACTION_TYPE_INC_TCP_ACK mlx5
> > > RTE_FLOW_ACTION_TYPE_DEC_TCP_ACK mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_DSCP mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_DSCP mlx5
> > > RTE_FLOW_ACTION_TYPE_OF_SET_VLAN_VID bnxt, cnxk, cxgbe, enic,
> > > mlx5, octeontx2, sfc
> > > RTE_FLOW_ACTION_TYPE_OF_SET_VLAN_PCP bnxt, cnxk, cxgbe, enic,
> > > mlx5, octeontx2, sfc
> > > RTE_FLOW_ACTION_TYPE_SET_TAG mlx5
> > > RTE_FLOW_ACTION_TYPE_SET_META mlx5
> > >
> > > This note deprecates the following RTE Flow actions:
> > > 1. As not supported by any of PMDs:
> > >
> > > RTE_FLOW_ACTION_TYPE_OF_SET_MPLS_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_DEC_MPLS_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_SET_NW_TTL
> > > RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_OUT
> > > RTE_FLOW_ACTION_TYPE_OF_COPY_TTL_IN
> > >
> > > 2. As supposed to be replaced by generig field modify action:
> > > RTE_FLOW_ACTION_TYPE_OF_DEC_NW_TTL
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_SRC
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_DST
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_SRC
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_DST
> > > RTE_FLOW_ACTION_TYPE_SET_TP_SRC
> > > RTE_FLOW_ACTION_TYPE_SET_TP_DST
> > > RTE_FLOW_ACTION_TYPE_DEC_TTL
> > > RTE_FLOW_ACTION_TYPE_SET_TTL
> > > RTE_FLOW_ACTION_TYPE_SET_MAC_SRC
> > > RTE_FLOW_ACTION_TYPE_SET_MAC_DST
> > > RTE_FLOW_ACTION_TYPE_INC_TCP_SEQ
> > > RTE_FLOW_ACTION_TYPE_DEC_TCP_SEQ
> > > RTE_FLOW_ACTION_TYPE_INC_TCP_ACK
> > > RTE_FLOW_ACTION_TYPE_DEC_TCP_ACK
> > > RTE_FLOW_ACTION_TYPE_SET_IPV4_DSCP
> > > RTE_FLOW_ACTION_TYPE_SET_IPV6_DSCP
> > > RTE_FLOW_ACTION_TYPE_SET_TAG
> > > RTE_FLOW_ACTION_TYPE_SET_META
> > >
> > > The VLAN set actions are interrelated to VLAN header
> > > insertion/removal and supported by multiple PMDs and supposed to be
> > > just deprecated but not be removed in 22.11.
> > >
> >
> > Why not remove them for v22.11? Do you think PMDs can't change the
> > existing implementation until 22.11?
> >
> > > Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> > >
> > > --
> > > v2 - deprecation.rst is updated
> > > v3 - doc comments addressed
> > > - commit message comments addressed
> > > - SET_VLAN_VID and SET_VLAN_PCP actions deprecated, but will not
> > > be removed in 22.11
> >
> > Deprecated symbols are to prevent new code using them, but for this
> > case there is no alternative, since PMDs still don't support
> > 'RTE_FLOW_ACTION_TYPE_MODIFY_FIELD' yet.
>
> This patch is not preventing new code using old actions, there are just
> comments to point to the new direction.
>
> > This patch is forcing users to use deprecated actions (except from mlx).
>
> I don't get it.
> It is encouraging to use the new generic action, which is supported only by
> mlx5 for now.
>
>
> > What about a slight change:
> > 1- In this release, update header/document as
> 'RTE_FLOW_ACTION_TYPE_MODIFY_FIELD'
> > is preferred way if supported. Instead of deprecating old ones.
>
> Deprecation is just a comment, clearly showing that it may be removed in
> future.
> In my opinion, it makes the message simple and clear.
>
>
> > 2- Have an agreement with PMD maintainers to switch to new action before
> v22.11,
> > and don't accept old action implementation in PMDs anymore.
> > Based on agreement update 'deprecation.rst' in this release to note that
> > old actions will be removed on v22.11.
> > (It would be good to have a check to prevent old actions merged
> > during that time.)
>
> Not sure I get it.
> You want to remove VLAN actions? I think it is premature.
>
> > 3- In v22.11, remove old actions, the PMDs that don't support
> MODIFY_FIELD
> > action will lose the feature.
>
> The VLAN actions are probably already used a lot in the field.
> I would consider removing them only if it becomes a burden to maintain.
+1
Dropping VLAN might trigger an avalanche of changes in applications - it is supported by multiple PMDs and should be widely engaged.
Other legacy actions are supported by very limited set of drivers and usage area should be smaller, I would say risk is moderate.
With best regards,
Slava
next prev parent reply other threads:[~2021-11-25 14:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 7:59 [PATCH] " Viacheslav Ovsiienko
2021-11-24 8:06 ` [PATCH v2] " Viacheslav Ovsiienko
2021-11-24 14:56 ` Thomas Monjalon
2021-11-24 15:37 ` [PATCH v3] " Viacheslav Ovsiienko
2021-11-24 15:59 ` Thomas Monjalon
2021-11-24 16:21 ` Ori Kam
2021-11-24 16:37 ` Slava Ovsiienko
2021-11-24 17:32 ` Thomas Monjalon
2021-11-24 18:09 ` Ori Kam
2021-11-25 11:53 ` Ferruh Yigit
2021-11-25 12:03 ` Somnath Kotur
2021-11-25 13:06 ` Thomas Monjalon
2021-11-25 14:13 ` Slava Ovsiienko [this message]
2021-11-25 14:40 ` Ferruh Yigit
2021-11-25 14:52 ` Slava Ovsiienko
2021-11-25 14:15 ` Ferruh Yigit
2021-11-25 13:56 ` Slava Ovsiienko
2021-11-25 15:14 ` Ferruh Yigit
2021-11-25 15:53 ` Thomas Monjalon
2021-11-25 12:18 ` Ferruh Yigit
2021-11-25 12:29 ` Ori Kam
2021-11-25 12:46 ` Ferruh Yigit
2021-11-25 13:56 ` Ori Kam
2021-11-25 14:28 ` Ferruh Yigit
2021-11-25 12:31 ` Ferruh Yigit
2021-11-25 12:50 ` Thomas Monjalon
2021-11-26 9:51 ` [PATCH v4] " Viacheslav Ovsiienko
2021-11-26 12:53 ` Ferruh Yigit
2021-11-26 13:06 ` Thomas Monjalon
2021-11-26 14:52 ` Olivier Matz
2021-11-26 17:07 ` Thomas Monjalon
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=DM6PR12MB3753CE024A99B824C19559BCDF629@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=orika@nvidia.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=somnath.kotur@broadcom.com \
--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).