From: "Margolin, Michael" <mrgolin@amazon.com>
To: Jason Gunthorpe <jgg@nvidia.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: Thu, 4 Jan 2024 11:50:33 +0200 [thread overview]
Message-ID: <3ae9207f-1159-42e6-a972-0dfb085e9f82@amazon.com> (raw)
In-Reply-To: <20240103133702.GN50406@nvidia.com>
On 1/3/2024 3:37 PM, Jason Gunthorpe wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Wed, Jan 03, 2024 at 03:33:41PM +0200, Margolin, Michael wrote:
>
>> I would like it to be as opaque as possible but on the other hand to express
>> that the mentioned 'interconnect path' relates specifically to PCI path.
> Who cares it is a "PCI path" if the the thing is totally invisible? It
> is some hidden implementation detail of your device that today happens
> to be PCI.
>
> There are many ways to get interconnect multipath coming, including
> PCIe UIO.
>
> Jason
Ok, changed according to your suggestion.
Michael
prev parent reply other threads:[~2024-01-04 9:51 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
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 [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=3ae9207f-1159-42e6-a972-0dfb085e9f82@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