public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	Linux RDMA list
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ewg <ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: broken support for UC in rdma_cm
Date: Mon, 15 Mar 2010 20:48:02 +0200	[thread overview]
Message-ID: <20100315184802.GA355@mtldesk030.lab.mtl.com> (raw)
In-Reply-To: <7E151C5823FF4048B15DCA15845BB0EB-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>

On Mon, Mar 15, 2010 at 08:38:00AM -0700, Sean Hefty wrote:
> 
> This is really a new feature request, which I may not have time to address.  It
> depends on the scope of the changes that are needed.
> 
> If both sides try using UC QPs, do you know what specific setting causes the
> connection to fail?

The actual failure is to modify the QP from init to rtr since the
attribute mask sets IB_QP_MAX_DEST_RD_ATOMIC and IB_QP_MIN_RNR_TIMER
which are invalid attributes in UC. The flags are set in
cm_init_qp_rtr_attr() since the transport is IB_QPT_RC. 
--
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:[~2010-03-15 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 11:12 broken support for UC in rdma_cm Eli Cohen
     [not found] ` <20100315111228.GC23358-8YAHvHwT2UEvbXDkjdHOrw/a8Rv0c6iv@public.gmane.org>
2010-03-15 13:45   ` Eli Cohen
     [not found]     ` <20100315134527.GA31210-8YAHvHwT2UEvbXDkjdHOrw/a8Rv0c6iv@public.gmane.org>
2010-03-15 15:38       ` Sean Hefty
     [not found]         ` <7E151C5823FF4048B15DCA15845BB0EB-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-03-15 18:48           ` Eli Cohen [this message]

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=20100315184802.GA355@mtldesk030.lab.mtl.com \
    --to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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