[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da1c7d5d-5faf-495f-af02-5b56b13d7f98@email.android.com>
Date: Sun, 22 Jul 2012 15:18:15 -0400
From: "Neil Horman <nhorman@...driver.com>" <nhorman@...driver.com>
To: David Miller <davem@...emloft.net>, vyasevich@...il.com
CC: netdev@...r.kernel.org, sri@...ibm.com, linux-sctp@...r.kernel.org,
joe@...ches.com
Subject: Re: [PATCH v6] sctp: Implement quick failover draft from tsvwg
Thanks all!
David Miller <davem@...emloft.net> wrote:
>From: Vlad Yasevich <vyasevich@...il.com>
>Date: Sun, 22 Jul 2012 14:18:12 -0400
>
>> Neil Horman <nhorman@...driver.com> wrote:
>>
>>>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@...driver.com>
> ...
>> Acked-by: Vlad Yasevich <vyasevich@...il.com>
>
>Applied, thanks everyone.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists