From: Michael Guralnik <michaelgur@nvidia.com>
To: <leonro@nvidia.com>, <jgg@nvidia.com>
Cc: <linux-rdma@vger.kernel.org>, <saeedm@nvidia.com>,
<tariqt@nvidia.com>, Michael Guralnik <michaelgur@nvidia.com>
Subject: [PATCH v2 rdma-next 0/8] Introduce mlx5 Memory Scheme ODP
Date: Mon, 9 Sep 2024 13:04:56 +0300 [thread overview]
Message-ID: <20240909100504.29797-1-michaelgur@nvidia.com> (raw)
This series introduces a new ODP scheme in mlx5 where the FW takes the
responsibility of parsing and providing page fault data to the driver
to handle the fault.
As opposed to the current ODP transport scheme where the driver is
responsible for reading and parsing work queues and querying mkeys to
acquire needed info to handle the page fault.
The new scheme allows driver to support ODP over Devx QPs where driver
is not able to access the QP buffers, owned by the user application,
to read the work queue requests.
Furthermore, the new scheme allows support for ODP with new indirect
MKEY types as the driver doesn't need to query or parse indirect mkeys
in this scheme.
The driver will enable the new scheme on devices that have the relevant
capabilities. Otherwise, transport scheme ODP will be the default.
The move to memory scheme ODP is transparent to existing ODP
applications and no change is needed.
New application that want to take advantage of the new functionality
should query which scheme is active and it's capabilities using Devx.
v1->v2:
- switch mlx5_umem_find_best_pgsz to a function and rename
Michael Guralnik (8):
net/mlx5: Expand mkey page size to support 6 bits
net/mlx5: Expose HW bits for Memory scheme ODP
RDMA/mlx5: Add new ODP memory scheme eqe format
RDMA/mlx5: Enforce umem boundaries for explicit ODP page faults
RDMA/mlx5: Split ODP mkey search logic
RDMA/mlx5: Add handling for memory scheme page fault events
RDMA/mlx5: Add implicit MR handling to ODP memory scheme
net/mlx5: Handle memory scheme ODP capabilities
drivers/infiniband/hw/mlx5/mlx5_ib.h | 30 +-
drivers/infiniband/hw/mlx5/mr.c | 10 +-
drivers/infiniband/hw/mlx5/odp.c | 400 ++++++++++++++----
.../net/ethernet/mellanox/mlx5/core/main.c | 54 ++-
include/linux/mlx5/device.h | 30 +-
include/linux/mlx5/mlx5_ifc.h | 64 ++-
6 files changed, 457 insertions(+), 131 deletions(-)
--
2.17.2
next reply other threads:[~2024-09-09 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 10:04 Michael Guralnik [this message]
2024-09-09 10:04 ` [PATCH v2 rdma-next 1/8] net/mlx5: Expand mkey page size to support 6 bits Michael Guralnik
2024-09-09 10:04 ` [PATCH v2 rdma-next 2/8] net/mlx5: Expose HW bits for Memory scheme ODP Michael Guralnik
2024-09-09 10:04 ` [PATCH v2 rdma-next 3/8] RDMA/mlx5: Add new ODP memory scheme eqe format Michael Guralnik
2024-09-09 10:05 ` [PATCH v2 rdma-next 4/8] RDMA/mlx5: Enforce umem boundaries for explicit ODP page faults Michael Guralnik
2024-09-09 10:05 ` [PATCH v2 rdma-next 5/8] RDMA/mlx5: Split ODP mkey search logic Michael Guralnik
2024-09-09 10:05 ` [PATCH v2 rdma-next 6/8] RDMA/mlx5: Add handling for memory scheme page fault events Michael Guralnik
2024-09-09 10:05 ` [PATCH v2 rdma-next 7/8] RDMA/mlx5: Add implicit MR handling to ODP memory scheme Michael Guralnik
2024-09-09 10:05 ` [PATCH v2 rdma-next 8/8] net/mlx5: Handle memory scheme ODP capabilities Michael Guralnik
2024-09-11 12:07 ` [PATCH v2 rdma-next 0/8] Introduce mlx5 Memory Scheme ODP Leon Romanovsky
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=20240909100504.29797-1-michaelgur@nvidia.com \
--to=michaelgur@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--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