Re: [PATCH mlx5-next V2 00/10] mlx5: Move data direct infrastructure to mlx5_core

[Leon Romanovsky]

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@xxxxxxxxxx>