and
or'ed into the modify mechanism.
Mike
-Original Message-
From: Hefty, Sean
Sent: Wednesday, October 03, 2012 6:39 PM
To: Doug Ledford; Marciniszyn, Mike; linux-rdma@vger.kernel.org
Subject: RE: Problem running rping over Intel adapters
1) rping, on the client side, clears
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
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
On 10/4/2012 10:01 AM, Hefty, Sean wrote:
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
We ran into this problem when testing rping over Intel/QLogic hardware:
[root@rdmaperf3 ~]# rping -s -a 172.31.2.103 -v
wait for CONNECTED state 10
connect error -1
cma event RDMA_CM_EVENT_REJECTED, error 28
[root@rdmaperf3 ~]#
[root@rdmaperf8 ~]# rping -c -a 172.31.2.103 -v -C 5
cma event
1) rping, on the client side, clears the conn_params for the newly to be
attempted connection, then sets:
conn_param.responder_resources = 1;
conn_param.initiator_depth = 1;
conn_param.retry_count = 10;
2) the qib driver enforces a maximum of 7 for retry_count. I don't
On 10/3/2012 5:50 PM, Hefty, Sean wrote:
1) rping, on the client side, clears the conn_params for the newly to be
attempted connection, then sets:
conn_param.responder_resources = 1;
conn_param.initiator_depth = 1;
conn_param.retry_count = 10;
2) the qib driver enforces a
1) rping, on the client side, clears the conn_params for the newly to be
attempted connection, then sets:
conn_param.responder_resources = 1;
conn_param.initiator_depth = 1;
conn_param.retry_count = 10;
2) the qib driver enforces a maximum of 7 for retry_count. I don't
On 10/3/2012 5:02 PM, Hefty, Sean wrote:
1) rping, on the client side, clears the conn_params for the newly to be
attempted connection, then sets:
conn_param.responder_resources = 1;
conn_param.initiator_depth = 1;
conn_param.retry_count = 10;
2) the qib driver
On 04/10/2012 03:47, Steve Wise wrote:
Not used by iwarp drivers...
Which one, the retry counter or the RNR retry counter?
Or.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at
10 matches
Mail list logo
