summaryrefslogtreecommitdiffstats
path: root/scripts/basic
diff options
context:
space:
mode:
authorNeil Horman <nhorman@tuxdriver.com>2012-07-21 07:56:07 +0000
committerDavid S. Miller <davem@davemloft.net>2012-07-22 12:13:46 -0700
commit5aa93bcf66f4af094d6f11096e81d5501a0b4ba5 (patch)
tree7bcf045fcae31a7e367e7eb1e0568b3702a25018 /scripts/basic
parente3906486f616da7cc086a3ba06c0df4e5a48b4ab (diff)
downloadblackbird-op-linux-5aa93bcf66f4af094d6f11096e81d5501a0b4ba5.tar.gz
blackbird-op-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 'scripts/basic')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud