DPDK patches and discussions
 help / color / mirror / Atom feed
From: Robin Jarry <rjarry@redhat.com>
To: dev@dpdk.org
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
	"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: [PATCH dpdk v2] rel_notes: announce 24.11 ipv6 api breakage
Date: Tue, 23 Jul 2024 10:27:46 +0200	[thread overview]
Message-ID: <20240723082745.31072-2-rjarry@redhat.com> (raw)
In-Reply-To: <20240722173936.24303-2-rjarry@redhat.com>

In 24.11, all IPv6 public APIs will be modified to use a structure
instead of fixed size arrays.

Signed-off-by: Robin Jarry <rjarry@redhat.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
---

Notes:
    v2: updated with the exhaustive list of symbols

 doc/guides/rel_notes/deprecation.rst | 42 ++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 6948641ff69b..bb17b78d193a 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -147,3 +147,45 @@ Deprecation Notices
   will be deprecated and subsequently removed in DPDK 24.11 release.
   Before this, the new port library API (functions rte_swx_port_*)
   will gradually transition from experimental to stable status.
+
+* net: A new IPv6 address structure will be introduced in DPDK 24.11.
+  It will replace all ad-hoc ``uint8_t[16]`` arrays in all public APIs and structures.
+  The following libraries and symbols are expected to be affected:
+
+  ethdev
+    - ``struct rte_flow_item_icmp6_nd_ns``
+    - ``struct rte_flow_item_icmp6_nd_na``
+    - ``struct rte_flow_action_set_ipv6``
+    - ``struct rte_flow_tunnel``
+  fib
+    - ``rte_fib6_add()``
+    - ``rte_fib6_delete()``
+    - ``rte_fib6_lookup_bulk()``
+  gro
+    - ``struct tcp6_flow_key``
+  hash
+    - ``struct rte_ipv6_tuple``
+  ipsec
+    - ``struct rte_ipsec_sadv6_key``
+  lpm
+    - ``rte_lpm6_add()``
+    - ``rte_lpm6_is_rule_present()``
+    - ``rte_lpm6_delete()``
+    - ``rte_lpm6_delete_bulk_func()``
+    - ``rte_lpm6_lookup()``
+    - ``rte_lpm6_lookup_bulk_func()``
+  net
+    - ``struct rte_ipv6_hdr``
+  node
+    - ``rte_node_ip6_route_add()``
+  pipeline
+    - ``struct rte_table_action_ipv6_header``
+  rib
+    - ``rte_rib6_lookup()``
+    - ``rte_rib6_lookup_exact()``
+    - ``rte_rib6_get_nxt()``
+    - ``rte_rib6_insert()``
+    - ``rte_rib6_remove()``
+    - ``rte_rib6_get_ip()``
+  table
+    - ``struct rte_table_lpm_ipv6_key``
-- 
2.45.2


  parent reply	other threads:[~2024-07-23  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 17:39 [PATCH dpdk] " Robin Jarry
2024-07-22 19:19 ` Morten Brørup
2024-07-23  8:27 ` Robin Jarry [this message]
2024-07-23  8:29   ` [PATCH dpdk v2] " Bruce Richardson
2024-07-23  8:48   ` Konstantin Ananyev
2024-07-25 17:28   ` Medvedkin, Vladimir
2024-07-31 10:52   ` 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=20240723082745.31072-2-rjarry@redhat.com \
    --to=rjarry@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.org \
    --cc=vladimir.medvedkin@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).