On Wed, Feb 13, 2008 at 09:05:24AM -0500, Jeff Squyres wrote:
> Actually, we should then also print out a different error message when
> RNR occurs in PP QP's, too. It should be something along the lines of
> "flow control problem occurred; this shouldn't happen..." (right now
> it says RNR
Actually, we should then also print out a different error message when
RNR occurs in PP QP's, too. It should be something along the lines of
"flow control problem occurred; this shouldn't happen..." (right now
it says RNR happened, and goes into detail into what that means -- but
that's no
Ok. I'll clean up the description of that MCA param to state that it
only applies to SRQs.
Thanks.
On Feb 13, 2008, at 12:59 AM, Gleb Natapov wrote:
On Tue, Feb 12, 2008 at 05:41:13PM -0500, Jeff Squyres wrote:
I see that in the OOB CPC for the openib BTL, when setting up the
send
side
On Tue, Feb 12, 2008 at 05:41:13PM -0500, Jeff Squyres wrote:
> I see that in the OOB CPC for the openib BTL, when setting up the send
> side of the QP, we set the rnr_retry value depending on whether the
> remote receive queue is a per-peer or SRQ:
>
> - SRQ: btl_openib_rnr_retry MCA param va
I see that in the OOB CPC for the openib BTL, when setting up the send
side of the QP, we set the rnr_retry value depending on whether the
remote receive queue is a per-peer or SRQ:
- SRQ: btl_openib_rnr_retry MCA param value
- PP: 0
The rationale given in a comment is that setting the RNR t
