From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jon Maloy <jon.maloy@ericsson.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
parthasarathy.bhuvaragan@ericsson.com, richard.alpe@ericsson.com,
ying.xue@windriver.com, maloy@donjonn.com,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next 3/3] tipc: reduce transmission rate of reset messages when link is down
Date: Tue, 5 Apr 2016 23:07:22 +0300 [thread overview]
Message-ID: <57041AFA.5090702@cogentembedded.com> (raw)
In-Reply-To: <1459873255-32354-4-git-send-email-jon.maloy@ericsson.com>
Hello.
On 04/05/2016 07:20 PM, Jon Maloy wrote:
> When a link is down, it will continuously try to re-establish contact
> with the peer by sending out a RESET or and ACTIVATE message at each
And/or?
> timeout interval. The default value for this interval is currently
> 375 ms. This is wasteful, and may become a problem in very large
> clusters with dozens or hundereds of nodes being down simultaneously.
Hundreds.
> We now introduce a simple backoff algorithm for these cases. The
> first five messages are sent at default rate; thereafter a message
> is sent only each 16't timer interval.
16th?
> This will cover the vast majority of link recyling cases, since the
Recycling.
> endpoint starting last will transmit at the higher speed, and the link
> should normally be established well be before the rate needs to be
> reduced.
>
> The only case where we will see a degradation of link re-establishment
> is when the endpoins remain intact, and a glitch in the transmission
Endpoints.
> media is causing the link reset. We will then experience a worst-case
> re-establishing time of 6 seconds, something we deem acceptable.
>
> Acked-by: Ying Xue <ying.xue@windriver.com>
> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
[...]
MBR, Sergei
prev parent reply other threads:[~2016-04-05 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 16:20 [PATCH net-next 0/3] tipc: some small fixes Jon Maloy
2016-04-05 16:20 ` [PATCH net-next 1/3] tipc: eliminate buffer leak in bearer layer Jon Maloy
2016-04-05 16:20 ` [PATCH net-next 2/3] tipc: stricter filtering of packets " Jon Maloy
2016-04-05 16:20 ` [PATCH net-next 3/3] tipc: reduce transmission rate of reset messages when link is down Jon Maloy
2016-04-05 20:07 ` Sergei Shtylyov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57041AFA.5090702@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=parthasarathy.bhuvaragan@ericsson.com \
--cc=paul.gortmaker@windriver.com \
--cc=richard.alpe@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).