On 8/16/2012 2:40 PM, Hefty, Sean wrote:
Is there a way to tune rdma_connect() timeout to a lower value ?
I don't believe so.
You could abort the connection by destroying the id after a specified amount of
time had expired.
Can cma_response_timeout and CMA_MAX_CM_RETRIES be made tunables ?
E
> Is there a way to tune rdma_connect() timeout to a lower value ?
I don't believe so.
You could abort the connection by destroying the id after a specified amount of
time had expired.
> Can cma_response_timeout and CMA_MAX_CM_RETRIES be made tunables ?
> Even better would have been if the call
> According to the OpenSM default configuration (/usr/sbin/opensm
> --create-config ) :
>
> # The subnet_timeout code that will be set for all the ports
> # The actual timeout is 4.096usec * 2^
> subnet_timeout 18
>
> # The code of maximal time a packet can live in a switch
> # The actu
Hi,
Le mercredi 18 juillet 2012 à 15:49 +, Hefty, Sean a écrit :
> > Is there a way to setup the timeout in rdma_connect() ?
>
> For IB, the timeout is based on the packet lifetime in the path record
> returned by the SA.
> The rdma_cm will retry a CM REQ the maximum number of times (15).
> Is there a way to setup the timeout in rdma_connect() ?
For IB, the timeout is based on the packet lifetime in the path record returned
by the SA. The rdma_cm will retry a CM REQ the maximum number of times (15).
> Is there a way to change the CM parameters ? e.g. "Service Timeout" to
> wait
