DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/6] eventdev: promote long-standing experimental API to stable
Date: Wed,  2 Sep 2026 08:53:53 -0700	[thread overview]
Message-ID: <20260902155722.577747-1-stephen@networkplumber.org> (raw)

The eventdev library still carries a number of experimental symbols that
have been unchanged for several releases. Per the ABI policy,
they are overdue for being promoted to stable.

This series removes the experimental tag from the eventdev API that was
added in v23.03 and v23.11 and has not changed since:

  - Rx adapter runtime parameters and create_ext_with_params
  - Tx adapter runtime parameters
  - crypto adapter runtime parameters
  - timer adapter remaining ticks get
  - event port link profiles
  - the DMA adapter API

With these patches the Tx, crypto and timer adapter source files have no
experimental symbols left at all.

Deliberately left experimental:

  - rte_event_eth_rx_adapter_queues_add(), added in v25.03, is too recent
  - the vector adapter API in rte_event_vector_adapter.h, also recent
  - the remaining experimental symbols in rte_eventdev.h

No functional change: this only swaps RTE_EXPORT_EXPERIMENTAL_SYMBOL for
RTE_EXPORT_SYMBOL, drops __rte_experimental from the headers, and updates
the release notes.  Since these symbols move out of the EXPERIMENTAL
section into the stable ABI, this must go into a major ABI release.


Stephen Hemminger (6):
  eventdev/eth_rx: promote adapter API to stable
  eventdev/eth_tx: promote adapter runtime params to stable
  eventdev/crypto: promote adapter runtime params to stable
  eventdev/timer: promote remaining ticks get to stable
  eventdev: promote link profile API to stable
  eventdev/dma: promote adapter API to stable

 doc/guides/rel_notes/release_26_11.rst  | 19 ++++++++++++++++
 lib/eventdev/rte_event_crypto_adapter.c |  6 ++---
 lib/eventdev/rte_event_crypto_adapter.h |  3 ---
 lib/eventdev/rte_event_dma_adapter.c    | 30 ++++++++++++-------------
 lib/eventdev/rte_event_dma_adapter.h    | 19 ----------------
 lib/eventdev/rte_event_eth_rx_adapter.c |  8 +++----
 lib/eventdev/rte_event_eth_rx_adapter.h |  4 ----
 lib/eventdev/rte_event_eth_tx_adapter.c |  6 ++---
 lib/eventdev/rte_event_eth_tx_adapter.h |  3 ---
 lib/eventdev/rte_event_timer_adapter.c  |  2 +-
 lib/eventdev/rte_event_timer_adapter.h  |  1 -
 lib/eventdev/rte_eventdev.c             |  8 +++----
 lib/eventdev/rte_eventdev.h             |  4 ----
 13 files changed, 49 insertions(+), 64 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-09-02 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 15:53 Stephen Hemminger [this message]
2026-09-02 15:53 ` [PATCH 1/6] eventdev/eth_rx: promote adapter API to stable Stephen Hemminger
2026-09-02 15:53 ` [PATCH 2/6] eventdev/eth_tx: promote adapter runtime params " Stephen Hemminger
2026-09-02 15:53 ` [PATCH 3/6] eventdev/crypto: " Stephen Hemminger
2026-09-02 16:34   ` Gujjar, Abhinandan S
2026-09-02 15:53 ` [PATCH 4/6] eventdev/timer: promote remaining ticks get " Stephen Hemminger
2026-09-02 15:53 ` [PATCH 5/6] eventdev: promote link profile API " Stephen Hemminger
2026-09-02 15:53 ` [PATCH 6/6] eventdev/dma: promote adapter " Stephen Hemminger

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=20260902155722.577747-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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