Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	mohan.krishna.ghanta.krishnamurthy@ericsson.com
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)	[thread overview]
Message-ID: <20180707.211625.1435722987348154525.davem@davemloft.net> (raw)
In-Reply-To: <1530883356-22355-1-git-send-email-jon.maloy@ericsson.com>

From: Jon Maloy <jon.maloy@ericsson.com>
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 <ying.xue@windriver.com>
> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>

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

      reply	other threads:[~2018-07-07 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 13:22 [net-next 1/1] tipc: extend link reset criteria for stale packet retransmission Jon Maloy
2018-07-07 12:16 ` David Miller [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=20180707.211625.1435722987348154525.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jon.maloy@ericsson.com \
    --cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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