summaryrefslogtreecommitdiffstats
path: root/mm/mempolicy.c
diff options
context:
space:
mode:
authorJon Paul Maloy <jon.maloy@ericsson.com>2016-04-15 13:33:04 -0400
committerDavid S. Miller <davem@davemloft.net>2016-04-15 16:09:05 -0400
commit88e8ac7000dc7ccf99975cc4070907e26a1027f9 (patch)
tree1b86555af16af03aca085e17c57508a8eb452e15 /mm/mempolicy.c
parent634696b197411e7a95b346d6e5c21841f29fcedd (diff)
downloadlinux-88e8ac7000dc7ccf99975cc4070907e26a1027f9.tar.bz2
tipc: reduce transmission rate of reset messages when link is down
When a link is down, it will continuously try to re-establish contact with the peer by sending out a RESET or an ACTIVATE message at each 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 hundreds of nodes being down simultaneously. 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 16th timer interval. This will cover the vast majority of link recycling cases, since the 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 times is when the endpoints remain intact, and a glitch in the transmission 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> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/mempolicy.c')
0 files changed, 0 insertions, 0 deletions