From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [net-next 1/1] tipc: extend link reset criteria for stale packet retransmission Date: Sat, 07 Jul 2018 21:16:25 +0900 (KST) Message-ID: <20180707.211625.1435722987348154525.davem@davemloft.net> References: <1530883356-22355-1-git-send-email-jon.maloy@ericsson.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net, mohan.krishna.ghanta.krishnamurthy@ericsson.com To: jon.maloy@ericsson.com Return-path: In-Reply-To: <1530883356-22355-1-git-send-email-jon.maloy@ericsson.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tipc-discussion-bounces@lists.sourceforge.net List-Id: netdev.vger.kernel.org From: Jon Maloy Date: Fri, 6 Jul 2018 15:22:36 +0200 > Currently a link is declared stale and reset if there has been 100 > repeated attempts to retransmit the same packet. However, in certain > infrastructures we see that packet (NACK) duplicates and delays may > cause such retransmit attempts to occur at a high rate, so that the > peer doesn't have a reasonable chance to acknowledge the reception > before the 100-limit is hit. This may take much less than the > stipulated link tolerance time, and despite that probe/probe replies > otherwise go through as normal. > > We now extend the criteria for link reset to also being time based. > I.e., we don't reset the link until the link tolerance time is passed > AND we have made 100 retransmissions attempts. > > Acked-by: Ying Xue > Signed-off-by: Jon Maloy Applied, thanks Jon. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot