public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Alan Cook
	<acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>,
	"Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Converting from RC to UC
Date: Sun, 13 Mar 2011 11:56:56 +0200	[thread overview]
Message-ID: <4D7C94E8.6070906@mellanox.com> (raw)
In-Reply-To: <loom.20110311T224601-402-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

  Alan Cook wrote:
> Roland Dreier<roland@...>  writes:
>> How are you setting up the connection? My understanding is that the RDMA CM (ie librdmacm) does not handle UC, so if you are using that, it shouldn't work.  Sean could confirm this.
>
> I am using RDMA CM.  I have not seen any documentation that states it does not support UC, although I have not seen any documentation that says it does either.   I have seen documentation regarding RDMA CM that talks about a connection not  actually being established between queue pairs when using unreliable datagram (UD), but nothing regarding support for UC.

Alan, you haven't specified if you app is user space or kernel space 
based,  I assume the former, I believe that it either just works or can 
be just made to work... e.g maybe a minor error on your side, or maybe 
something small to change/complete on the rdma-cm side...

I'm copying the maintainer of the kernel rdma-cm and librdmacm, Sean - 
should there any problem for librdmacm consumers to use UC at their apps?

Or.

--
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:[~2011-03-13  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 18:29 Converting from RC to UC Alan Cook
     [not found] ` <loom.20110311T192125-878-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-11 18:58   ` Jason Gunthorpe
2011-03-11 20:10     ` Alan Cook
     [not found]     ` <AANLkTikqv-WYcL3_=5HRU6mVORLydNgcqv-5_VYkJrbC@mail.gmail.com>
     [not found]       ` <AANLkTikqv-WYcL3_=5HRU6mVORLydNgcqv-5_VYkJrbC-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-11 21:54         ` Jason Gunthorpe
2011-03-11 21:57           ` Alan Cook
2011-03-11 21:42   ` Roland Dreier
2011-03-11 21:55     ` Alan Cook
     [not found]       ` <loom.20110311T224601-402-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-11 22:07         ` Jason Gunthorpe
2011-03-13  9:56         ` Or Gerlitz [this message]
2011-03-14  1:08           ` Alan Cook
     [not found]             ` <loom.20110314T020520-335-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-14 15:05               ` frank zago
     [not found]     ` <AANLkTimM0PDiWuHFJfn3s-JVEKWHVVfL4+2Kcc4+G5C7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-14 15:26       ` Hefty, Sean

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=4D7C94E8.6070906@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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