Netdev List
 help / color / mirror / Atom feed
From: Damian Lukowski <damian@tvk.rwth-aachen.de>
To: Netdev <netdev@vger.kernel.org>
Subject: [PATCH 0/3] [v3] Revert Backoff on ICMP destination unreachable
Date: Wed, 26 Aug 2009 12:16:22 +0200	[thread overview]
Message-ID: <4A950B76.1070002@tvk.rwth-aachen.de> (raw)

This series of patches implements the TCP improvement of the Internet Draft
"Make TCP more Robust to Long Connectivity Disruptions"
(http://tools.ietf.org/html/draft-zimmermann-tcp-lcd).

Exponential backoff is TCP's standard behaviour during long connectivity
disruptions, which is a countermeasure against network congestion.
If congestion can be excluded as the reason for RTO retransmission loss,
backoff is not desirable, as it yields longer TCP recovery times, when
the communication path is repaired shortly after an unsuccessful
retransmission probe.

1) This patch renames the skb in tcp_v4_err() in preparation for patch 2.
2) Contains the main reversion logic.
   Reintroduces tcp_bound_rto() and __tcp_set_rto()
3) This patch modifies the interpretation of the tcp_retries{1,2} sysctls.
   It became necessary because with patch2 the assumption that the number
   of retransmits corresponds to an specific timeout value is not accurate
   anymore. With this patch tcp_retries{1,2} specifies a timeout value,
   equivalent to the time a connection with an rto value of MIN_RTO (200ms)
   would need to retransmit N segments. IOW: The meaning (in sense of time)
   is mostly preserved, but the actual connection timeout does not depend
   on the calculated rto of the connection, anymore.

Signed-off-by: Damian Lukowski <damian@tvk.rwth-aachen.de>
---

             reply	other threads:[~2009-08-26 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 10:16 Damian Lukowski [this message]
2009-08-31  4:56 ` [PATCH 0/3] [v3] Revert Backoff on ICMP destination unreachable David Miller
2009-09-01  9:56 ` David Miller

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=4A950B76.1070002@tvk.rwth-aachen.de \
    --to=damian@tvk.rwth-aachen.de \
    --cc=netdev@vger.kernel.org \
    /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