From: Raslan Darawsheh <rasland@nvidia.com>
To: Shani Peretz <shperetz@nvidia.com>, dev@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH] net/mlx5: add RSS TIR registration API
Date: Thu, 8 Jan 2026 18:12:24 +0200 [thread overview]
Message-ID: <2a1c0ecc-5792-48c1-936b-d03ce7874a7e@nvidia.com> (raw)
In-Reply-To: <20260108081232.5420-1-shperetz@nvidia.com>
Hi,
On 08/01/2026 10:12 AM, Shani Peretz wrote:
> mlx5 PMD is a bifurcated driver, which uses rdma-core APIs to
> communicate with HW instead of UIO or VFIO directly.
>
> It is possible for external libraries built on rdma-core to steer
> traffic to DPDK-managed Rx queues using mlx5dv flow API. This
> requires access to TIR object handles.
>
> TIR (Transport Interface Receive) is a hardware object that defines
> how incoming packets are distributed across Rx queues. It encodes
> the complete RSS configuration including the hash function type,
> hash key, set of destination queues, and which packet fields
> (IP addresses, ports, etc.) participate in the hash calculation.
> When a flow rule uses a TIR as its destination, the hardware applies
> this RSS configuration to matching packets.
>
> Add the following functions to mlx5 PMD private API:
>
> - rte_pmd_mlx5_rss_tir_register(): Create a TIR DevX object based on
> the provided RSS configuration. The returned TIR handle can be used
> as a destination action in mlx5dv flow steering APIs from rdma-core.
>
> - rte_pmd_mlx5_rss_tir_unregister(): Release the TIR object when no
> longer needed.
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-01-08 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 8:12 Shani Peretz
2026-01-08 16:12 ` Raslan Darawsheh [this message]
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=2a1c0ecc-5792-48c1-936b-d03ce7874a7e@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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).