public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: "robert-4JaGZRWAfWbajFs6igw21g@public.gmane.org"
	<robert-4JaGZRWAfWbajFs6igw21g@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Is SRP over RoCE possible?
Date: Tue, 14 Feb 2017 23:51:23 +0000	[thread overview]
Message-ID: <1487116271.2466.29.camel@sandisk.com> (raw)
In-Reply-To: <CAANLjFqrKYdAyj-c0avvnjFEmiMuQ5zc5wYzuPmNjAHgZOUo4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, 2017-02-14 at 16:43 -0700, Robert LeBlanc wrote:
> I got things running with SRP and SCST and I could not get the hang
> with SRP. Thanks for your help.

Hello Robert,

Thank you for the testing and for the feedback to the linux-rdma mailing
list. If switching to the NVMe-over-Fabrics protocol is not a valid
alternative on your setup I think this means that it would be valuable
to have SRP-over-RoCE support upstream ...

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:[~2017-02-14 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 18:24 Is SRP over RoCE possible? Robert LeBlanc
     [not found] ` <CAANLjFoJEnRERRNm34u8yonJCDqAe1d68BYb_GBTmmxVpFxpZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-14 18:45   ` Bart Van Assche
     [not found]     ` <1487097898.2466.8.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-02-14 19:07       ` Robert LeBlanc
2017-02-14 20:34       ` Robert LeBlanc
     [not found]         ` <CAANLjFqEk8MJ9+BQrqq7VFfuzbhrL=X_ht4r=qnRHLt8MOTdXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-14 20:36           ` Bart Van Assche
     [not found]             ` <1487104602.2466.17.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-02-14 20:52               ` Robert LeBlanc
     [not found]                 ` <CAANLjFonC2UJpCSgkuRXXGdUVEa7sg0Lb9tzHpxp0zM0vit+hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-14 23:43                   ` Robert LeBlanc
     [not found]                     ` <CAANLjFqrKYdAyj-c0avvnjFEmiMuQ5zc5wYzuPmNjAHgZOUo4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-14 23:51                       ` Bart Van Assche [this message]
     [not found]                         ` <1487116271.2466.29.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-02-15  1:10                           ` Robert LeBlanc
     [not found]                             ` <CAANLjFp8ybkAwqHdoBXVtdCgnLXnqjxE-gewB4MMR-s3zj168g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-15  4:32                               ` Bart Van Assche
     [not found]                                 ` <1487132923.20239.2.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-02-16  0:46                                   ` Robert LeBlanc
2017-02-14 20:43           ` Robert LeBlanc

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=1487116271.2466.29.camel@sandisk.com \
    --to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robert-4JaGZRWAfWbajFs6igw21g@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