DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Jarry <rjarry@redhat.com>
To: dev@dpdk.org
Subject: [PATCH dpdk] doc: announce rte_graph ABI changes for 26.11
Date: Fri, 17 Jul 2026 11:01:22 +0200	[thread overview]
Message-ID: <20260717090121.1859773-2-rjarry@redhat.com> (raw)

The graph library internal scheduling will change from a circular
buffer to a topological bitmap. This affects struct rte_graph and
struct rte_node layouts.

Signed-off-by: Robin Jarry <rjarry@redhat.com>
---
 doc/guides/rel_notes/deprecation.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index f5c12cc74762..6183f33b893a 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -61,6 +61,13 @@ Deprecation Notices
 * mempool: The object array in ``struct rte_mempool_cache`` is oversize by factor two,
   and will be reduced to ``RTE_MEMPOOL_CACHE_MAX_SIZE`` in DPDK 26.11.
 
+* graph: The internal scheduling mechanism of ``struct rte_graph`` will change
+  in DPDK 26.11. The circular buffer fields (``head``, ``tail``, ``cir_mask``,
+  ``cir_start``) will be replaced with a topological bitmap scheduler.
+  A new field will be added to ``struct rte_node`` for the scheduling order.
+  The graph walk functions will process nodes in topological order using bitmap
+  scanning instead of the circular buffer.
+
 * lib: will fix extending some enum/define breaking the ABI. There are multiple
   samples in DPDK that enum/define terminated with a ``.*MAX.*`` value which is
   used by iterators, and arrays holding these values are sized with this
-- 
2.55.0


             reply	other threads:[~2026-07-17  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  9:01 Robin Jarry [this message]
2026-07-21 10:23 ` [PATCH dpdk] doc: announce rte_graph ABI changes for 26.11 Jerin Jacob
2026-07-21 11:51   ` Bruce Richardson
2026-07-22 12:50     ` Thomas Monjalon
2026-07-21 11:49 ` David Marchand

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=20260717090121.1859773-2-rjarry@redhat.com \
    --to=rjarry@redhat.com \
    --cc=dev@dpdk.org \
    /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