From: Bart Van Assche <bvanassche@acm.org>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Hal Rosenstock <hal@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
oulijun <oulijun@huawei.com>
Subject: Re: [PATCH] RDMA/srpt: Filter out AGN bits
Date: Mon, 19 Aug 2019 08:45:58 -0700 [thread overview]
Message-ID: <ad0d3211-bf70-d349-7e14-e4b515bb3e98@acm.org> (raw)
In-Reply-To: <20190819151722.GG5080@mellanox.com>
On 8/19/19 8:17 AM, Jason Gunthorpe wrote:
> On Mon, Aug 19, 2019 at 08:11:21AM -0700, Bart Van Assche wrote:
>> Does uniqueness of the I/O controller GUID only matter in InfiniBand
>> networks or does it also matter in other RDMA networks?
>>
>> How about using 0 as default value for the srpt_service_guid in RoCE
>> networks?
>
> How does SRP connection management even work on RoCE?? The CM MADs
> still carry a service_id? How do the sides exchange the service ID to
> start the connection? Or is it ultimately overriden in the CM to use
> an IP port based service ID?
The ib_srpt kernel driver would have to set id_ext to a unique value if
srpt_service_guid would be zero since the SRP initiator kernel driver
uses the IOC GUID + id_ext + initiator_ext combination in its connection
uniqueness check (srp_conn_unique()).
The ib_srp kernel driver supports both the IB/CM and the RDMA/CM. The
srp_daemon software tells ib_srp to use the IB/CM. Software like
blktests tells ib_srp to use the RDMA/CM. From
https://github.com/osandov/blktests/blob/master/tests/srp/rc:
srp_single_login \
"id_ext=$ioc_guid,ioc_guid=$ioc_guid,dest=$dest,$add_param" \
"$p/add_target"
The most important parameter in the login string is $dest. That is a
string with the following format:
<IP address>:<port number>.
Bart.
next prev parent reply other threads:[~2019-08-19 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 15:15 [PATCH] RDMA/srpt: Filter out AGN bits Bart Van Assche
2019-08-19 12:21 ` Jason Gunthorpe
2019-08-19 13:40 ` Hal Rosenstock
2019-08-19 13:46 ` Jason Gunthorpe
2019-08-19 13:49 ` Hal Rosenstock
2019-08-19 15:11 ` Bart Van Assche
2019-08-19 15:17 ` Jason Gunthorpe
2019-08-19 15:45 ` Bart Van Assche [this message]
2019-08-19 16:16 ` Jason Gunthorpe
2019-08-19 16:48 ` Bart Van Assche
2019-08-20 17:08 ` Doug Ledford
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=ad0d3211-bf70-d349-7e14-e4b515bb3e98@acm.org \
--to=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=hal@mellanox.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=oulijun@huawei.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