Get rid of transport layer retry count config parameter
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Get rid of transport layer retry count config parameter
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines
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.
Quoted 5 lines
Quoted 2 lines
Isn't there some IB protocol level rationale for a low retry count in various fabric setups?
IIRC the retry count is part of what drives the APM switch over, so APM configuration should use a lower value.
Completely agree Jason. Lowering the retry_count is very useful for APM (Automatic Path Migration).