From: Leon Romanovsky <leon@kernel.org>
To: linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
Cosmin Ratiu <cratiu@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Dragos Tatulea <dtatulea@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Gal Pressman <gal@nvidia.com>, Jakub Kicinski <kuba@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
open list <linux-kernel@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH mlx5-next V2 00/10] mlx5: Move data direct infrastructure to mlx5_core
Date: Thu, 01 Oct 2026 11:41:25 -0400 [thread overview]
Message-ID: <179086928533.370711.525345553365862636.b4-ty@kernel.org> (raw)
In-Reply-To: <20260930114227.139274-1-tariqt@nvidia.com>
On Wed, 30 Sep 2026 14:42:17 +0300, Tariq Toukan wrote:
> Data direct support currently lives in mlx5_ib, which owns the data
> direct PCI driver, device matching and resource management. To prepare
> for data direct support in netdev, move this infrastructure to mlx5_core
> and provide a common interface for its consumers.
>
> The series first replaces the direct IB unbind callback with a blocking
> notifier chain, allowing multiple consumers to receive unbind events.
> It then separates consumer registration from initialization,
> consolidates the per-device state and resources, and keeps IB-specific
> locking and MR teardown in mlx5_ib.
>
> [...]
Applied, thanks!
[01/10] RDMA/mlx5: Notify data direct users via a notifier chain on unbind
https://git.kernel.org/rdma/rdma/c/a727a424068b5d
[02/10] RDMA/mlx5: Add mlx5_data_direct_supported() helper
https://git.kernel.org/rdma/rdma/c/2365f8d7f609cf
[03/10] RDMA/mlx5: Make the data direct VUID query self-contained
https://git.kernel.org/rdma/rdma/c/ebbb9f87689998
[04/10] RDMA/mlx5: Give the data direct PCI driver a proper name
https://git.kernel.org/rdma/rdma/c/0a4095faca722b
[05/10] RDMA/mlx5: Move and rename data direct resource functions
https://git.kernel.org/rdma/rdma/c/47723d4febd62b
[06/10] RDMA/mlx5: Add new registration stage for data direct users
https://git.kernel.org/rdma/rdma/c/1c879b1e9f2ed6
[07/10] RDMA/mlx5: Extract IB specific lock out of data direct
https://git.kernel.org/rdma/rdma/c/26f27809b0034e
[08/10] RDMA/mlx5: Consolidate data direct state into one object
https://git.kernel.org/rdma/rdma/c/f6c452b311f0e4
[09/10] RDMA/mlx5: Pull data_direct resource creation in init phase
https://git.kernel.org/rdma/rdma/c/7611034dc86cfd
[10/10] mlx5: Move data direct implementation to mlx5_core
https://git.kernel.org/rdma/rdma/c/00290b9ff59ef4
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-10-01 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:42 [PATCH mlx5-next V2 00/10] mlx5: Move data direct infrastructure to mlx5_core Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 01/10] RDMA/mlx5: Notify data direct users via a notifier chain on unbind Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 02/10] RDMA/mlx5: Add mlx5_data_direct_supported() helper Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 03/10] RDMA/mlx5: Make the data direct VUID query self-contained Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 04/10] RDMA/mlx5: Give the data direct PCI driver a proper name Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 05/10] RDMA/mlx5: Move and rename data direct resource functions Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 06/10] RDMA/mlx5: Add new registration stage for data direct users Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 07/10] RDMA/mlx5: Extract IB specific lock out of data direct Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 08/10] RDMA/mlx5: Consolidate data direct state into one object Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 09/10] RDMA/mlx5: Pull data_direct resource creation in init phase Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 10/10] mlx5: Move data direct implementation to mlx5_core Tariq Toukan
2026-10-01 15:41 ` Leon Romanovsky [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=179086928533.370711.525345553365862636.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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