From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Margolin <mrgolin@amazon.com>
Cc: leon@kernel.org, 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 v3] RDMA/efa: Add EFA query MR support
Date: Mon, 11 Dec 2023 13:50:19 -0400 [thread overview]
Message-ID: <20231211175019.GK2944114@nvidia.com> (raw)
In-Reply-To: <20231211174715.7369-1-mrgolin@amazon.com>
On Mon, Dec 11, 2023 at 05:47:15PM +0000, Michael Margolin wrote:
> diff --git a/drivers/infiniband/hw/efa/efa_admin_cmds_defs.h b/drivers/infiniband/hw/efa/efa_admin_cmds_defs.h
> index 9c65bd27bae0..597f7ca6f31d 100644
> --- a/drivers/infiniband/hw/efa/efa_admin_cmds_defs.h
> +++ b/drivers/infiniband/hw/efa/efa_admin_cmds_defs.h
> @@ -415,6 +415,32 @@ struct efa_admin_reg_mr_resp {
> * memory region
> */
> u32 r_key;
> +
> + /*
> + * 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;
> +
> + /*
> + * Physical PCIe bus used by the device to reach the MR for receive
> + * operation
> + */
> + u8 recv_pci_bus_id;
> +
> + /*
> + * Physical PCIe bus used by the device to reach the MR for RDMA read
> + * operation
> + */
> + u8 rdma_read_pci_bus_id;
> +
> + /*
> + * Physical PCIe bus used by the device to reach the MR for RDMA write
> + * receive
> + */
> + u8 rdma_recv_pci_bus_id;
What driver is bound to this other PCIe bus and how did the iommu get
setup for it?
Jason
next prev parent reply other threads:[~2023-12-11 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 17:47 [PATCH for-next v3] RDMA/efa: Add EFA query MR support Michael Margolin
2023-12-11 17:50 ` Jason Gunthorpe [this message]
2023-12-13 17:05 ` Margolin, Michael
2023-12-21 13:45 ` Margolin, Michael
2023-12-25 11:26 ` Leon Romanovsky
2024-01-02 23:47 ` Jason Gunthorpe
2024-01-03 13:33 ` Margolin, Michael
2024-01-03 13:37 ` Jason Gunthorpe
2024-01-04 9:50 ` Margolin, Michael
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=20231211175019.GK2944114@nvidia.com \
--to=jgg@nvidia.com \
--cc=anasmous@amazon.com \
--cc=firasj@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=leon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox