public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"Marciniszyn,
	Mike" <mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Problem running rping over Intel adapters
Date: Thu, 04 Oct 2012 09:27:30 -0500	[thread overview]
Message-ID: <506D9CD2.20606@opengridcomputing.com> (raw)
In-Reply-To: <506D2174.10601-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 10/4/2012 12:41 AM, Or Gerlitz wrote:
> On 04/10/2012 03:47, Steve Wise wrote:
>>
>> Not used by iwarp drivers...
>
> Which one, the retry counter or the RNR retry counter?
>

rnr_retry_count has no meaning in iWARP.  There is no RNR message in the 
iwarp protocol.  For some iwarp devices (cxgb3 for example), an ingress 
send with no recv buffer available results in immediate connection 
termination.   Some devices, (eg cxgb4), the ingress SEND is buffered in 
the adapter until a recv buf is posted.  Both behaviors are allowed in 
the iwarp specs.

retry_count, I assume, is for connection establishment?  For the Chelsio 
devices, this is all up to the TCP stack and thus this counter is not 
used.  If there is no TCP listener, then the connection establishment 
will fail immediately.  If the node is not reachable, then normal TCP 
retransmit rules apply, but once TCP gives up, then the rdma connection 
establishment will fail.

Also, the RDMA_CM and IW_CM don't even pass these two counters down to 
the drivers' connect function.  See struct iw_cm_conn_param and 
cma.c/cma_connect_iw() iwcm.c/iw_cm_connect().


Steve.

> 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

--
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:[~2012-10-04 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 21:40 Problem running rping over Intel adapters Doug Ledford
     [not found] ` <506CB0E9.90201-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-10-03 21:50   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A8237346A98E58-Q3cL8pyY+6ukrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-03 21:57       ` Doug Ledford
     [not found]         ` <506CB4D8.4010604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-10-03 22:02           ` Hefty, Sean
     [not found]             ` <1828884A29C6694DAF28B7E6B8A8237346A98E8E-Q3cL8pyY+6ukrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-03 22:05               ` Doug Ledford
2012-10-04  1:47               ` Steve Wise
     [not found]                 ` <506CEAC1.9070808-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2012-10-04  5:41                   ` Or Gerlitz
     [not found]                     ` <506D2174.10601-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-10-04 14:27                       ` Steve Wise [this message]
     [not found]                         ` <506D9CD2.20606-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2012-10-04 15:01                           ` Hefty, Sean
     [not found]                             ` <1828884A29C6694DAF28B7E6B8A8237346A99126-Q3cL8pyY+6ukrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-04 15:08                               ` Steve Wise
2012-10-03 22:38   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A8237346A98ECB-Q3cL8pyY+6ukrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-04 13:55       ` Marciniszyn, Mike

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=506D9CD2.20606@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@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