public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Lukas Sismis <sismis@dyna-nic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v7 2/6] ethdev: add RSS type helper APIs
Date: Wed, 28 Jan 2026 17:16:55 -0800	[thread overview]
Message-ID: <20260128171655.398e9871@phoenix.local> (raw)
In-Reply-To: <20260128215838.73502-3-sismis@dyna-nic.com>

On Wed, 28 Jan 2026 22:58:34 +0100
Lukas Sismis <sismis@dyna-nic.com> wrote:

> --- a/doc/guides/rel_notes/release_26_03.rst
> +++ b/doc/guides/rel_notes/release_26_03.rst
> @@ -55,6 +55,17 @@ New Features
>       Also, make sure to start the actual text at the margin.
>       =======================================================
>  
> +* **Added experimental RSS type helper APIs in ethdev.**
> +
> +  Added new experimental APIs ``rte_eth_rss_type_info_get()``,
> +  ``rte_eth_rss_type_from_str()``, and ``rte_eth_rss_type_to_str()`` to
> +  convert between RSS type names and values. These helpers provide a global
> +  RSS type string table via ``struct rte_eth_rss_type_info``.
> +
> +* **Added experimental port and queue identifier typedefs in ethdev.**
> +
> +  Added new experimental typedefs ``rte_port_id_t`` and ``rte_queue_id_t``
> +  to provide type-safe identifiers for Ethernet device ports and queues.
>  

I would rather see this library work without the addition of typedefs for this.
The types for port and queue should be typedef'd but it should be its own
patch series and fix it everywhere, "yes that would be a very big patch".

Introducing it in middle of other library addition means it would
only be partially done and create lots of confusion.

  reply	other threads:[~2026-01-29  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 21:58 [PATCH v7 0/6] flow_parser: add shared parser library Lukas Sismis
2026-01-28 21:58 ` [PATCH v7 1/6] cmdline: include stddef.h for MSVC compatibility Lukas Sismis
2026-01-28 21:58 ` [PATCH v7 2/6] ethdev: add RSS type helper APIs Lukas Sismis
2026-01-29  1:16   ` Stephen Hemminger [this message]
2026-01-28 21:58 ` [PATCH v7 4/6] app/testpmd: use shared flow parser library Lukas Sismis
2026-01-28 21:58 ` [PATCH v7 5/6] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-01-28 21:58 ` [PATCH v7 6/6] test: add flow parser library functional tests Lukas Sismis

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=20260128171655.398e9871@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=sismis@dyna-nic.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