Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: "Margolin, Michael" <mrgolin@amazon.com>
To: Gal Pressman <gal.pressman@linux.dev>, <jgg@nvidia.com>,
	<leon@kernel.org>, <linux-rdma@vger.kernel.org>
Cc: <sleybo@amazon.com>, <matua@amazon.com>,
	Anas Mousa <anasmous@amazon.com>,
	Firas Jahjah <firasj@amazon.com>
Subject: Re: [PATCH for-next] RDMA/efa: Add EFA query MR support
Date: Wed, 6 Dec 2023 20:30:37 +0200	[thread overview]
Message-ID: <3df3da6b-9c8b-4bea-b9e0-25f2a06f71e5@amazon.com> (raw)
In-Reply-To: <08c5ccbe-1f9a-4e4d-b6bd-91ef62ef1b5b@linux.dev>

Hey Gal,

Thanks for your comments.

On 12/6/2023 4:52 PM, Gal Pressman wrote:
> Hi Michael,
>
> On 06/12/2023 0:16, Michael Margolin wrote:
>> @@ -432,6 +435,9 @@ static int efa_ib_device_add(struct efa_dev *dev)
>>
>>       ib_set_device_ops(&dev->ibdev, &efa_dev_ops);
>>
>> +     if (IS_ENABLED(CONFIG_INFINIBAND_USER_ACCESS))
> EFA depends on CONFIG_INFINIBAND_USER_ACCESS:
>
>       7 config INFINIBAND_EFA
>       8         tristate "Amazon Elastic Fabric Adapter (EFA) support"
>       9         depends on PCI_MSI && 64BIT && !CPU_BIG_ENDIAN
>      10         depends on INFINIBAND_USER_ACCESS

I'll remove this if statement.

>> +             dev->ibdev.driver_def = efa_uapi_defs;
>> +
>>       err = ib_register_device(&dev->ibdev, "efa_%d", &pdev->dev);
>>       if (err)
>>               goto err_destroy_eqs;
>> diff --git a/drivers/infiniband/hw/efa/efa_verbs.c b/drivers/infiniband/hw/efa/efa_verbs.c
>> index 0f8ca99d0827..d81904f4b876 100644
>> --- a/drivers/infiniband/hw/efa/efa_verbs.c
>> +++ b/drivers/infiniband/hw/efa/efa_verbs.c
>> @@ -13,6 +13,9 @@
>>  #include <rdma/ib_user_verbs.h>
>>  #include <rdma/ib_verbs.h>
>>  #include <rdma/uverbs_ioctl.h>
>> +#define UVERBS_MODULE_NAME efa_ib
>> +#include <rdma/uverbs_named_ioctl.h>
>> +#include <rdma/ib_user_ioctl_cmds.h>
>>
>>  #include "efa.h"
>>  #include "efa_io_defs.h"
>> @@ -1653,6 +1656,9 @@ static int efa_register_mr(struct ib_pd *ibpd, struct efa_mr *mr, u64 start,
>>       mr->ibmr.lkey = result.l_key;
>>       mr->ibmr.rkey = result.r_key;
>>       mr->ibmr.length = length;
>> +     mr->recv_pci_bus_id = result.recv_pci_bus_id;
>> +     mr->rdma_read_pci_bus_id = result.rdma_read_pci_bus_id;
>> +     mr->rdma_recv_pci_bus_id = result.rdma_recv_pci_bus_id;
> Why is a query_mr ioctl better than returning this data through udata on
> MR creation?

We need this for both reg_user_mr and reg_user_mr_dmabuf and it doesn't
make sense to implement it twice. In addition, those two verbs are using
different mechanisms (write and ioctl) and extending dmabuf reg_mr will
require more extensive changes on rdma-core side.

Michael


  reply	other threads:[~2023-12-06 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 22:16 [PATCH for-next] RDMA/efa: Add EFA query MR support Michael Margolin
2023-12-06 14:52 ` Gal Pressman
2023-12-06 18:30   ` Margolin, Michael [this message]
2023-12-07  7:23     ` 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=3df3da6b-9c8b-4bea-b9e0-25f2a06f71e5@amazon.com \
    --to=mrgolin@amazon.com \
    --cc=anasmous@amazon.com \
    --cc=firasj@amazon.com \
    --cc=gal.pressman@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matua@amazon.com \
    --cc=sleybo@amazon.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