From: Leon Romanovsky <leon@kernel.org>
To: Michael Margolin <mrgolin@amazon.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, sleybo@amazon.com,
matua@amazon.com, gal.pressman@linux.dev,
Anas Mousa <anasmous@amazon.com>,
Firas Jahjah <firasj@amazon.com>
Subject: Re: [PATCH for-next v2] RDMA/efa: Add EFA query MR support
Date: Mon, 11 Dec 2023 10:10:32 +0200 [thread overview]
Message-ID: <20231211081032.GB4870@unreal> (raw)
In-Reply-To: <20231207142748.10345-1-mrgolin@amazon.com>
On Thu, Dec 07, 2023 at 02:27:48PM +0000, Michael Margolin wrote:
> Add EFA driver uapi definitions and register a new query MR method that
> currently returns the physical PCI buses' IDs the device is using to
> reach the MR. Update admin definitions and efa-abi accordingly.
>
> Reviewed-by: Anas Mousa <anasmous@amazon.com>
> Reviewed-by: Firas Jahjah <firasj@amazon.com>
> Signed-off-by: Michael Margolin <mrgolin@amazon.com>
> ---
> drivers/infiniband/hw/efa/efa.h | 5 +-
> .../infiniband/hw/efa/efa_admin_cmds_defs.h | 31 ++++++++
> drivers/infiniband/hw/efa/efa_com_cmd.c | 6 ++
> drivers/infiniband/hw/efa/efa_com_cmd.h | 4 +
> drivers/infiniband/hw/efa/efa_main.c | 5 ++
> drivers/infiniband/hw/efa/efa_verbs.c | 77 +++++++++++++++++++
> include/uapi/rdma/efa-abi.h | 19 +++++
> 7 files changed, 146 insertions(+), 1 deletion(-)
<...>
> + /*
> + * Mask indicating which fields have valid values
> + * 0 : recv_pci_bus_id
> + * 1 : rdma_read_pci_bus_id
> + * 2 : rdma_recv_pci_bus_id
> + */
> + u8 validity;
<...>
> #define EFA_GID_SIZE 16
> +#define EFA_INVALID_PCI_BUS_ID 0xffff
Is 0xffff value guaranteed by PCI subsystem to be invalid? Why don't you
provide "validity" field to userspace instead?
Thanks
next prev parent reply other threads:[~2023-12-11 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 14:27 [PATCH for-next v2] RDMA/efa: Add EFA query MR support Michael Margolin
2023-12-11 8:10 ` Leon Romanovsky [this message]
2023-12-11 10:35 ` Margolin, Michael
2023-12-11 11:26 ` Leon Romanovsky
2023-12-11 17:46 ` Margolin, Michael
2023-12-12 7:20 ` 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=20231211081032.GB4870@unreal \
--to=leon@kernel.org \
--cc=anasmous@amazon.com \
--cc=firasj@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@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 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.