From: Jason Gunthorpe <jgg@nvidia.com>
To: Zhu Yanjun <yanjun.zhu@intel.com>
Cc: mustafa.ismail@intel.com, shiraz.saleem@intel.com,
leon@kernel.org, linux-rdma@vger.kernel.org,
Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCHv4 for-next 1/1] RDMA/irdma: Add support for dmabuf pin memory regions
Date: Fri, 17 Feb 2023 16:37:47 -0400 [thread overview]
Message-ID: <Y+/lm2FHuPISyh2C@nvidia.com> (raw)
In-Reply-To: <20230217011425.498847-1-yanjun.zhu@intel.com>
On Fri, Feb 17, 2023 at 09:14:25AM +0800, Zhu Yanjun wrote:
> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> This is a followup to the EFA dmabuf[1]. Irdma driver currently does
> not support on-demand-paging(ODP). So it uses habanalabs as the
> dmabuf exporter, and irdma as the importer to allow for peer2peer
> access through libibverbs.
>
> In this commit, the function ib_umem_dmabuf_get_pinned() is used.
> This function is introduced in EFA dmabuf[1] which allows the driver
> to get a dmabuf umem which is pinned and does not require move_notify
> callback implementation. The returned umem is pinned and DMA mapped
> like standard cpu umems, and is released through ib_umem_release().
>
> [1]https://lore.kernel.org/lkml/20211007114018.GD2688930@ziepe.ca/t/
>
> Reviewed-by: Shiraz Saleem <shiraz.saleem@intel.com>
> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
> ---
> V3->V4: Remove inlen test
> V2->V3: Remove unnecessary variable initialization;
> Use error handler;
> V1->V2: Thanks Shiraz Saleem, he gave me a lot of good suggestions.
> This commit is based on the shared functions from refactored
> irdma_reg_user_mr.
> ---
> drivers/infiniband/hw/irdma/verbs.c | 42 +++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2023-02-17 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 1:14 [PATCHv4 for-next 1/1] RDMA/irdma: Add support for dmabuf pin memory regions Zhu Yanjun
2023-02-17 20:37 ` Jason Gunthorpe [this message]
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=Y+/lm2FHuPISyh2C@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=shiraz.saleem@intel.com \
--cc=yanjun.zhu@intel.com \
--cc=yanjun.zhu@linux.dev \
/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.