diff options
author | Neil Horman <nhorman@tuxdriver.com> | 2012-07-21 09:56:07 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2012-07-22 21:13:46 +0200 |
commit | 5aa93bcf66f4af094d6f11096e81d5501a0b4ba5 (patch) | |
tree | 7bcf045fcae31a7e367e7eb1e0568b3702a25018 /drivers/net | |
parent | net: fix race condition in several drivers when reading stats (diff) | |
download | linux-5aa93bcf66f4af094d6f11096e81d5501a0b4ba5.tar.xz linux-5aa93bcf66f4af094d6f11096e81d5501a0b4ba5.zip |
sctp: Implement quick failover draft from tsvwg
I've seen several attempts recently made to do quick failover of sctp transports
by reducing various retransmit timers and counters. While its possible to
implement a faster failover on multihomed sctp associations, its not
particularly robust, in that it can lead to unneeded retransmits, as well as
false connection failures due to intermittent latency on a network.
Instead, lets implement the new ietf quick failover draft found here:
http://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
This will let the sctp stack identify transports that have had a small number of
errors, and avoid using them quickly until their reliability can be
re-established. I've tested this out on two virt guests connected via multiple
isolated virt networks and believe its in compliance with the above draft and
works well.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
CC: Vlad Yasevich <vyasevich@gmail.com>
CC: Sridhar Samudrala <sri@us.ibm.com>
CC: "David S. Miller" <davem@davemloft.net>
CC: linux-sctp@vger.kernel.org
CC: joe@perches.com
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions