[PATCH rdma-next 00/11] RDMA/mlx5: Preparation for SD support
From: Edward Srouji
Date: Tue Nov 17 2026 - 09:02:23 EST
This series prepares mlx5_ib for Socket Direct (SD), where one IB device
spans several core devices, one per PCIe function. Today the driver
assumes a single core device per IB device and reaches it through
dev->mdev all over the code.
Instead, each call site now finds its core device through the resource
it works on: QPs, SRQs, AHs and MWs through their PD, and DEVX objects,
UARs and mmaps through their ucontext. A CQ and an MR store the core
device they were created on, since they cannot always reach their owner
when they need it. The SD series can then change where a resource lives
in the resolvers, without touching the call sites.
The resolvers follow one naming scheme: <resource>_to_mdev() returns a
core device and <resource>_to_dev() an IB device. Where several resource
types are accepted, a _Generic() dispatches to per-type helpers, which
are prefixed with '__' and are not meant to be called directly.
State kept once per IB device, such as the ODP page-fault EQ, delay drop
and local loopback, stays on dev->mdev. The SD series decides how each
of them works across core devices.
This series only changes how each call site finds its core device. With
one core device per IB device every resolver returns dev->mdev, so the
behaviour is unchanged. Pre-existing issues in the touched code are
intentionally left alone so that each patch stays a mechanical
conversion.
Patches 1-2: name device pointers consistently, dev for the IB device
and mdev for the core device.
Patches 3-7: resolve the core device through the PD.
Patches 8-11: resolve the core device through the ucontext, and keep it
on the CQ.
Signed-off-by: Edward Srouji <edwards@xxxxxxxxxx>
---
Akiva Goldberger (11):
RDMA/mlx5: Enforce dev/mdev naming for device pointers
RDMA/mlx5: Rename to_mdev() helpers that return an IB device
RDMA/mlx5: Select the PD and SRQ core device through the PD
RDMA/mlx5: Select the core device through PD for QP commands
RDMA/mlx5: Cache the MR core device and resolve the MW's via its PD
RDMA/mlx5: Select the AH core device through their PD
RDMA/mlx5: Select the QP core device through its PD
RDMA/mlx5: Resolve core device from ucontext for DEVX resources
RDMA/mlx5: Cache the CQ core device and resolve it via cq_to_mdev()
RDMA/mlx5: Resolve the bfreg UAR-index core device from the ucontext
RDMA/mlx5: Resolve UAR and mmap core devices via the ucontext
drivers/infiniband/hw/mlx5/ah.c | 20 +-
drivers/infiniband/hw/mlx5/cmd.c | 52 +--
drivers/infiniband/hw/mlx5/cmd.h | 26 +-
drivers/infiniband/hw/mlx5/counters.c | 32 +-
drivers/infiniband/hw/mlx5/cq.c | 120 +++----
drivers/infiniband/hw/mlx5/devx.c | 159 ++++-----
drivers/infiniband/hw/mlx5/devx.h | 10 +-
drivers/infiniband/hw/mlx5/dm.c | 74 +++--
drivers/infiniband/hw/mlx5/dmah.c | 10 +-
drivers/infiniband/hw/mlx5/fs.c | 32 +-
drivers/infiniband/hw/mlx5/gsi.c | 27 +-
drivers/infiniband/hw/mlx5/ib_rep.c | 48 +--
drivers/infiniband/hw/mlx5/ib_virt.c | 12 +-
drivers/infiniband/hw/mlx5/macsec.c | 10 +-
drivers/infiniband/hw/mlx5/mad.c | 18 +-
drivers/infiniband/hw/mlx5/main.c | 270 +++++++--------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 151 +++++++--
drivers/infiniband/hw/mlx5/mr.c | 228 +++++++------
drivers/infiniband/hw/mlx5/odp.c | 64 ++--
drivers/infiniband/hw/mlx5/qos.c | 13 +-
drivers/infiniband/hw/mlx5/qp.c | 580 +++++++++++++++++----------------
drivers/infiniband/hw/mlx5/qp.h | 34 +-
drivers/infiniband/hw/mlx5/qpc.c | 109 ++++---
drivers/infiniband/hw/mlx5/restrack.c | 15 +-
drivers/infiniband/hw/mlx5/srq.c | 50 +--
drivers/infiniband/hw/mlx5/srq.h | 4 +-
drivers/infiniband/hw/mlx5/srq_cmd.c | 124 ++++---
drivers/infiniband/hw/mlx5/std_types.c | 10 +-
drivers/infiniband/hw/mlx5/umr.c | 133 ++++----
drivers/infiniband/hw/mlx5/umr.h | 22 +-
drivers/infiniband/hw/mlx5/wr.c | 15 +-
31 files changed, 1330 insertions(+), 1142 deletions(-)
---
base-commit: 36d1eca030a37baa00a56bf34962f36263181918
change-id: 20261117-mlx5-sd-prep-571490a1fad3
Best regards,
--
Edward Srouji <edwards@xxxxxxxxxx>