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 [email protected]
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
