On 06/22/2016 09:15 AM, Christoph Hellwig wrote:
On Wed, Jun 22, 2016 at 03:05:59PM +0300, Sagi Grimberg wrote:
This parameter was added in order to support a proper timeout for
error recovery before the spec defined a periodic keep-alive.
Now that we have periodic keep-alive, we don't need a user configurable
transport layer retry count, the keep-alive timeout is sufficient,
transports can retry for as long as they see fit.
Isn't there some IB protocol level rationale for a low retry count
in various fabric setups?
The IB spec defines an end-to-end credit mechanism for RC connections.
So if the transport layer is reliable (InfiniBand, RoCE with DCB
enabled) setting the retry count high enough is only needed to avoid
connection shutdown due to brief cable disconnect/reconnect events.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
