From: Tariq Toukan <tariqt@nvidia.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Cosmin Ratiu <cratiu@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Eric Dumazet <edumazet@google.com>, Gal Pressman <gal@nvidia.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
Leon Romanovsky <leonro@nvidia.com>,
open list <linux-kernel@vger.kernel.org>,
Leon Romanovsky <leon@kernel.org>, <linux-rdma@vger.kernel.org>,
Mark Bloch <mbloch@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: [pull-request] mlx5: Move data direct infrastructure to mlx5_core
Date: Sun, 4 Oct 2026 09:49:21 +0300 [thread overview]
Message-ID: <20261004064921.213888-1-tariqt@nvidia.com> (raw)
Hi,
The following pull-request contains common mlx5 updates
for your *net-next* tree.
Please pull and let me know of any problem.
Find more details below [1].
Regards,
Tariq
[1]
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.
With these preparations in place, the final patch moves the shared
implementation and PCI driver to mlx5_core. Data direct initialization
and resource creation run during core load, before consumers attach;
cleanup runs during core unload, after consumers detach.
The data direct PCI driver is also explicitly named "mlx5_dd", replacing
the previous "mlx5_ib" name derived from KBUILD_MODNAME.
This series prepares the shared infrastructure for netdev support.
The netdev consumer will follow in a separate series.
----------------------------------------------------------------
The following changes since commit 36b1d3299d0b6aa51485cc9a79b8d94948d5f3d4:
net/mlx5: Add qp_latency_sensitive_disable cap bit (2026-07-27 02:35:16 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next
for you to fetch changes up to 00290b9ff59ef47b990d26a6b1a8b2ea6dedf5e9:
mlx5: Move data direct implementation to mlx5_core (2026-10-01 11:40:42 -0400)
----------------------------------------------------------------
Dragos Tatulea (10):
RDMA/mlx5: Notify data direct users via a notifier chain on unbind
RDMA/mlx5: Add mlx5_data_direct_supported() helper
RDMA/mlx5: Make the data direct VUID query self-contained
RDMA/mlx5: Give the data direct PCI driver a proper name
RDMA/mlx5: Move and rename data direct resource functions
RDMA/mlx5: Add new registration stage for data direct users
RDMA/mlx5: Extract IB specific lock out of data direct
RDMA/mlx5: Consolidate data direct state into one object
RDMA/mlx5: Pull data_direct resource creation in init phase
mlx5: Move data direct implementation to mlx5_core
drivers/infiniband/hw/mlx5/Makefile | 1 -
drivers/infiniband/hw/mlx5/cmd.c | 21 --
drivers/infiniband/hw/mlx5/cmd.h | 2 -
drivers/infiniband/hw/mlx5/data_direct.c | 227 ------------
drivers/infiniband/hw/mlx5/data_direct.h | 23 --
drivers/infiniband/hw/mlx5/main.c | 144 ++------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 18 +-
drivers/infiniband/hw/mlx5/mr.c | 7 +-
drivers/infiniband/hw/mlx5/odp.c | 2 +-
drivers/infiniband/hw/mlx5/std_types.c | 3 +-
drivers/infiniband/hw/mlx5/umr.c | 11 +-
drivers/net/ethernet/mellanox/mlx5/core/Makefile | 2 +-
.../net/ethernet/mellanox/mlx5/core/data_direct.c | 400 +++++++++++++++++++++
drivers/net/ethernet/mellanox/mlx5/core/main.c | 15 +
.../net/ethernet/mellanox/mlx5/core/mlx5_core.h | 5 +
include/linux/mlx5/data_direct.h | 47 +++
include/linux/mlx5/driver.h | 8 +
17 files changed, 515 insertions(+), 421 deletions(-)
delete mode 100644 drivers/infiniband/hw/mlx5/data_direct.c
delete mode 100644 drivers/infiniband/hw/mlx5/data_direct.h
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/data_direct.c
create mode 100644 include/linux/mlx5/data_direct.h
next reply other threads:[~2026-10-04 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 6:49 Tariq Toukan [this message]
2026-10-07 2:00 ` patchwork-bot+netdevbpf
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=20261004064921.213888-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--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 \
/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
all inboxes | Powered by JetHome®