rdma_connect() timeout question
Hello,
Is there a way to tune rdma_connect() timeout to a lower value ?
With CMA_CM_RESPONSE_TIMEOUT as 20 and CMA_MAX_CM_RETRIES 15,
it takes about a minute to timeout. We would like to tune it in our case to a much lower value.
The scenario is RDS trying to reconnect when a bonding interface notifies us of a link fail over.
In our setup the gratuitous arp doesn't arrive sometimes to update the arp entry with the new GID.
The address resolution returns the old GID. Route resolution also happens to return the old path in this failure case. (Other times when route solution fails it is not a problem. The reconnect attempts eventually go through in those cases.) And the rdma_connect() gets stuck. A timeout in 1 minute and a subsequent retry of address/route-resolution/rdma_connect then succeeds. Because by that time the arp entry is updated.
Can cma_response_timeout and CMA_MAX_CM_RETRIES be made tunables ?
Even better would have been if the caller (RDS in this case) could have passed them as connection setup parameters. ;-) That way we don't have to disturb the setting for non-RDS traffic.
Venkat
--
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
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line
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.
Quoted 4 lines
Can
cma_response_timeoutandCMA_MAX_CM_RETRIESbe made tunables ? Even better would have been if the caller (RDS in this case) could have passed them as connection setup parameters. ;-)
That way we don't have to disturb the setting for non-RDS traffic.
A per rdma_cm_id option for this makes sense to me.
iWarp developers, would timeout/retry values be usable for iwarp? --
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
A message that is not in the archive (sent off-list or not yet received): 1828884A29C6694DAF28B7E6B8A8237346A899E6-P5GAC/[email protected]
Quoted 5 lines · Sean
Quoted 1 line
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.
Quoted 7 lines
Quoted 4 lines
Can
cma_response_timeoutandCMA_MAX_CM_RETRIESbe made tunables ? Even better would have been if the caller (RDS in this case) could have passed them as connection setup parameters. ;-)
That way we don't have to disturb the setting for non-RDS traffic.A per
rdma_cm_idoption for this makes sense to me.iWarp developers, would timeout/retry values be usable for iwarp?
I think this would be useful for the iwarp side too. Not sure yet exactly how it would apply for cxgb3/4 though...
--
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