From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>, Zhu Yanjun <yanjun.zhu@intel.com>
Cc: mustafa.ismail@intel.com, shiraz.saleem@intel.com,
leon@kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCHv3 for-next 1/1] RDMA/irdma: Add support for dmabuf pin memory regions
Date: Fri, 17 Feb 2023 08:46:52 +0800 [thread overview]
Message-ID: <073e4d3b-f451-27f9-716a-2cd2e51d8535@linux.dev> (raw)
In-Reply-To: <Y+5FuSxVrtmCawC8@nvidia.com>
在 2023/2/16 23:03, Jason Gunthorpe 写道:
> On Wed, Feb 01, 2023 at 11:21:15AM +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/
>>
>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>> Reviewed-by: Shiraz Saleem <shiraz.saleem@intel.com>
>> ---
>> 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 | 45 +++++++++++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>>
>> diff --git a/drivers/infiniband/hw/irdma/verbs.c b/drivers/infiniband/hw/irdma/verbs.c
>> index 6982f38596c8..7525f4cdf6fb 100644
>> --- a/drivers/infiniband/hw/irdma/verbs.c
>> +++ b/drivers/infiniband/hw/irdma/verbs.c
>> @@ -2977,6 +2977,50 @@ static struct ib_mr *irdma_reg_user_mr(struct ib_pd *pd, u64 start, u64 len,
>> return ERR_PTR(err);
>> }
>>
>> +static struct ib_mr *irdma_reg_user_mr_dmabuf(struct ib_pd *pd, u64 start,
>> + u64 len, u64 virt,
>> + int fd, int access,
>> + struct ib_udata *udata)
>> +{
>> + struct irdma_device *iwdev = to_iwdev(pd->device);
>> + struct ib_umem_dmabuf *umem_dmabuf;
>> + struct irdma_mr *iwmr;
>> + int err;
>> +
>> + if (len > iwdev->rf->sc_dev.hw_attrs.max_mr_size)
>> + return ERR_PTR(-EINVAL);
>> +
>> + if (udata->inlen < IRDMA_MEM_REG_MIN_REQ_LEN)
>> + return ERR_PTR(-EINVAL);
> Shiraz is correct, I'm wondering how this even works. This is a new
> style uAPI without UVERBS_ATTR_UHW so inlen should always be 0.
Got it. Thanks Shiraz and Jason.
I will remove the test of inlen in the latest commit.
Best Regards,
Zhu Yanjun
>
> How did you manage to test this??
>
> Jason
next prev parent reply other threads:[~2023-02-17 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 3:21 [PATCHv3 for-next 1/1] RDMA/irdma: Add support for dmabuf pin memory regions Zhu Yanjun
2023-02-03 3:16 ` Zhu Yanjun
2023-02-15 13:38 ` Saleem, Shiraz
2023-02-17 1:27 ` Zhu Yanjun
2023-02-16 15:03 ` Jason Gunthorpe
2023-02-17 0:46 ` Zhu Yanjun [this message]
2023-02-17 2:23 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 22:37 Zhu Yanjun
2023-01-05 13:37 ` Jason Gunthorpe
2023-01-07 6:22 ` Yanjun Zhu
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=073e4d3b-f451-27f9-716a-2cd2e51d8535@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=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 \
/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;
as well as URLs for NNTP newsgroup(s).