[ofa-general] rdma cm timeout option, was [iWARP issues]

[Talpey, Thomas]

At 02:15 PM 12/10/2007, Caitlin Bestler wrote:
>So there is need for *some* mechanism to timeout a stalled iWARP connectionion
>process even after a valid TCP connection is established. A vendor
>specific, non-
>configurable, method is probably more than adequate. But *something* has to be
>there, you cannot just rely on the TCP mechanisms. Nor can you assume that the
>TCP stack servicing RDMA connections has the same defaults as the host stack.

Yes, protection from upper layer timeouts is important. But I'm not
certain whether you're advocating a CM layer timeout, or a vendor-
specific requirement in each card's lower stack.

I tend to prefer the latter - to avoid assumptions in the CM. At
connection time, CM can't tell the difference between a TCP delay
and an MPA delay. This could lead to bad assumptions and misleading
errors.

Tom.