All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Michael Guralnik <michaelgur@nvidia.com>,
	leonro@nvidia.com, jgg@nvidia.com
Cc: linux-rdma@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com
Subject: Re: [PATCH rdma-next 0/8] Introduce mlx5 Memory Scheme ODP
Date: Fri, 6 Sep 2024 13:35:46 +0800	[thread overview]
Message-ID: <4e8e01d1-359d-4877-ac6c-29f4fc512fb7@linux.dev> (raw)
In-Reply-To: <20240904153038.23054-1-michaelgur@nvidia.com>

在 2024/9/4 23:30, Michael Guralnik 写道:
> 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.

On-Demand-Paging (ODP) is a technique to alleviate much of the 
shortcomings of memory registration. Applications no longer need to pin 
down the underlying physical pages of the address space, and track the 
validity of the mappings. Rather, the HCA requests the latest 
translations from the OS when pages are not present, and the OS 
invalidates translations which are no longer valid due to either 
non-present pages or mapping changes.

As such, it seems that it can save memory via not pinning down the 
underlying physical pages of the address space, and track the validity 
of the mappings.

What is the difference on the performance with/without ODP enabled? And 
about memory usage, is there any test result about this?

And ODP can be used mlx5 IB device? Or ODP can only be used in mlx5 
RoCEv2 device?

Thanks,
Zhu Yanjun

> 
> 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          |  17 +-
>   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, 449 insertions(+), 126 deletions(-)
> 


  parent reply	other threads:[~2024-09-06  5:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 15:30 [PATCH rdma-next 0/8] Introduce mlx5 Memory Scheme ODP Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 1/8] net/mlx5: Expand mkey page size to support 6 bits Michael Guralnik
2024-09-04 16:18   ` Jason Gunthorpe
2024-09-05 20:48     ` Michael Guralnik
2024-09-05 23:21       ` Jason Gunthorpe
2024-09-04 15:30 ` [PATCH rdma-next 2/8] net/mlx5: Expose HW bits for Memory scheme ODP Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 3/8] RDMA/mlx5: Add new ODP memory scheme eqe format Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 4/8] RDMA/mlx5: Enforce umem boundaries for explicit ODP page faults Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 5/8] RDMA/mlx5: Split ODP mkey search logic Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 6/8] RDMA/mlx5: Add handling for memory scheme page fault events Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 7/8] RDMA/mlx5: Add implicit MR handling to ODP memory scheme Michael Guralnik
2024-09-04 15:30 ` [PATCH rdma-next 8/8] net/mlx5: Handle memory scheme ODP capabilities Michael Guralnik
2024-09-06  5:35 ` Zhu Yanjun [this message]
2024-09-08  6:18   ` [PATCH rdma-next 0/8] Introduce mlx5 Memory Scheme ODP Michael Guralnik
2024-09-09  2:10     ` Zhu Yanjun

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=4e8e01d1-359d-4877-ac6c-29f4fc512fb7@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michaelgur@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.