From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Ori Kam <orika@nvidia.com>, Ferruh Yigit <ferruh.yigit@amd.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [PATCH 2/2] doc: update deprecation notice of flow items
Date: Thu, 24 Nov 2022 15:26:59 +0100 [thread overview]
Message-ID: <20221124142659.3350953-3-thomas@monjalon.net> (raw)
In-Reply-To: <20221124142659.3350953-1-thomas@monjalon.net>
The flow items are not yet cleaned up in DPDK 22.11 as desired.
The plan is updated for this release, with more details.
A new plan must be precised during the next release.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/rel_notes/deprecation.rst | 37 ++++++++++++++++++++++------
1 file changed, 29 insertions(+), 8 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8e4b1c08ff..a780c5b126 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -55,14 +55,35 @@ Deprecation Notices
One solution can be using a fixed size array instead of ``.*MAX.*`` value.
* ethdev: The flow API matching pattern structures, ``struct rte_flow_item_*``,
- should start with relevant protocol header.
- Some matching pattern structures implements this by duplicating protocol header
- fields in the struct. To clarify the intention and to be sure protocol header
- is intact, will replace those fields with relevant protocol header struct.
- In v21.02 both individual protocol header fields and the protocol header struct
- will be added as union, target is switch usage to the protocol header by time.
- In v21.11 LTS, protocol header fields will be cleaned and only protocol header
- struct will remain.
+ should start with relevant protocol header structure from lib/net/.
+ The individual protocol header fields and the protocol header struct
+ may be kept together in an union as a first migration step.
+
+ These items are not compliant (not including struct from lib/net/):
+
+ - ``rte_flow_item_ah``
+ - ``rte_flow_item_arp_eth_ipv4``
+ - ``rte_flow_item_e_tag``
+ - ``rte_flow_item_geneve``
+ - ``rte_flow_item_geneve_opt``
+ - ``rte_flow_item_gre``
+ - ``rte_flow_item_gtp``
+ - ``rte_flow_item_icmp6``
+ - ``rte_flow_item_icmp6_nd_na``
+ - ``rte_flow_item_icmp6_nd_ns``
+ - ``rte_flow_item_icmp6_nd_opt``
+ - ``rte_flow_item_icmp6_nd_opt_sla_eth``
+ - ``rte_flow_item_icmp6_nd_opt_tla_eth``
+ - ``rte_flow_item_igmp``
+ - ``rte_flow_item_ipv6_ext``
+ - ``rte_flow_item_l2tpv3oip``
+ - ``rte_flow_item_mpls``
+ - ``rte_flow_item_nsh``
+ - ``rte_flow_item_nvgre``
+ - ``rte_flow_item_pfcp``
+ - ``rte_flow_item_pppoe``
+ - ``rte_flow_item_pppoe_proto_id``
+ - ``rte_flow_item_vxlan_gpe``
* ethdev: Queue specific stats fields will be removed from ``struct rte_eth_stats``.
Mentioned fields are: ``q_ipackets``, ``q_opackets``, ``q_ibytes``, ``q_obytes``,
--
2.36.1
next prev parent reply other threads:[~2022-11-24 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 14:26 [PATCH 0/2] update ethdev deprecation notices Thomas Monjalon
2022-11-24 14:26 ` [PATCH 1/2] doc: update deprecation notice of legacy flow actions Thomas Monjalon
2022-11-24 14:26 ` Thomas Monjalon [this message]
2022-11-24 14:35 ` [PATCH 0/2] update ethdev deprecation notices Andrew Rybchenko
2022-11-24 14:36 ` Ori Kam
2022-11-25 10:00 ` 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=20221124142659.3350953-3-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=orika@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).