public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: Tom Talpey <tom-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>,
	Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Parav Pandit
	<pandit.parav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RDMA/CM and multiple QPs
Date: Tue, 8 Sep 2015 08:07:42 -0700	[thread overview]
Message-ID: <55EEF9BE.2010002@sandisk.com> (raw)
In-Reply-To: <55EEE936.3060702-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>

On 09/08/2015 06:57 AM, Tom Talpey wrote:
> On 9/6/2015 11:15 AM, Bart Van Assche wrote:
>> On 09/06/15 00:50, Christoph Hellwig wrote:
>>> Note that the SRP driver already in tree is a good example for this,
>>> although it doesn't use RDMA/CM and thus already operates on a
>>> per-ib_device level.
>>
>> The challenges with regard to adding RDMA/CM support to the SRP
>> initiator and target drivers are:
>> - IANA has not yet assigned a port number to the SRP protocol (see e.g.
>>
>> http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml).
>
> IANA doesn't do this automatically. Has anyone made the request?
>
> You might want to think through why it needs a dedicated port number
> though. iSER reuses the iSCSI port, by negotiating RDMA during login.

iSER is an iSCSI transport and that is why iSER reuses the iSCSI port 
number. SRP is a SCSI transport protocol by itself and that is why a new 
port number is needed for the SRP protocol.

>> - The login request (struct srp_login_req) is too large for the RDMA/CM.
>>     A format for the login parameters for the RDMA/CM has not yet been
>>     standardized.
>
> Are you suggesting that RDMA/CM perform the login? That seems
> like a layering issue.

Sorry but I don't see why this would be a layering issue.

Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-09-08 15:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06  6:45 RDMA/CM and multiple QPs Christoph Hellwig
     [not found] ` <20150906064550.GA30683-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-09-06  7:42   ` Parav Pandit
     [not found]     ` <CAG53R5VZDZKiuR-jLybS1PhrT9K4GG6xTr8bOG-L0VaQgqEXSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-06  7:50       ` Christoph Hellwig
     [not found]         ` <20150906075024.GA7845-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-09-06  7:54           ` Parav Pandit
     [not found]             ` <CAG53R5UsH3aEmRf2EgNYydJ=cMZCFG19ZQjHcLn=NjQxsnwf-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-07  5:08               ` Christoph Hellwig
2015-09-06 15:15           ` Bart Van Assche
     [not found]             ` <55EC5879.202-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-09-08 13:57               ` Tom Talpey
     [not found]                 ` <55EEE936.3060702-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>
2015-09-08 15:07                   ` Bart Van Assche [this message]
2015-09-08 12:32   ` Sagi Grimberg
     [not found]     ` <55EED54B.7090608-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-09-08 13:14       ` Christoph Hellwig
     [not found]         ` <20150908131407.GB5316-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-09-10  9:50           ` Sagi Grimberg
     [not found]             ` <55F15269.2060200-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-09-10 13:29               ` Christoph Hellwig
     [not found]                 ` <20150910132927.GA6440-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-09-10 13:52                   ` Sagi Grimberg
2015-09-10 16:30   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A82373A903A082-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-09-10 17:55       ` Parav Pandit

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=55EEF9BE.2010002@sandisk.com \
    --to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pandit.parav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=tom-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org \
    /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