All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Alan Cook <acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Converting from RC to UC
Date: Fri, 11 Mar 2011 11:58:31 -0700	[thread overview]
Message-ID: <20110311185831.GX22729@obsidianresearch.com> (raw)
In-Reply-To: <loom.20110311T192125-878-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

On Fri, Mar 11, 2011 at 06:29:19PM +0000, Alan Cook wrote:
> I currently have a working RDMA InfiniBand based client-server application using
> Reliable Connection (RC) service.  I would like to change the application to use
> Unreliable Connection (UC) service.  I am not performing RDMA reads, so I should
> be able to use UC.
> 
> I was under the impression that the only change that would be required would be
> changing the queue pair type from IBV_QPT_RC to IBV_QPT_UC.  After making this
> change on both the client and server applications, I receive an Invalid
> Parameter error from rdma_accept() on the server side of the application.  The
> client side reports no errors (other than the rejected server connection).
> 
> Internet searches have not been fruitful, as it seems most people are using RC
> rather than UC.
> 
> What else needs to be changed in the setup for switching from RC to UC?

I think what you are hitting is some code is calling ibv_modify_qp
with an invalid qp_attr_mask for one of the state transitions. UC and
RC have different requirements. Assuming you are not calling
ibv_modify_qp in your app it is probably a kernel bug?

Jason
--
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-11 18:58 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 [this message]
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
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=20110311185831.GX22729@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.