netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ycheng@google.com
Cc: ilpo.jarvinen@helsinki.fi, ncardwell@google.com,
	nanditad@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] tcp: detect loss above high_seq in recovery
Date: Sun, 22 Jan 2012 14:24:16 -0500 (EST)	[thread overview]
Message-ID: <20120122.142416.403336311074678485.davem@davemloft.net> (raw)
In-Reply-To: <1327020141-26883-1-git-send-email-ycheng@google.com>

From: Yuchung Cheng <ycheng@google.com>
Date: Thu, 19 Jan 2012 16:42:21 -0800

> Correctly implement a loss detection heuristic: New sequences (above
> high_seq) sent during the fast recovery are deemed lost when higher
> sequences are SACKed.
> 
> Current code does not catch these losses, because tcp_mark_head_lost()
> does not check packets beyond high_seq. The fix is straight-forward by
> checking packets until the highest sacked packet. In addition, all the
> FLAG_DATA_LOST logic are in-effective and redundant and can be removed.
> 
> Update the loss heuristic comments. The algorithm above is documented
> as heuristic B, but it is redundant too because heuristic A already
> covers B.
> 
> Note that this change only marks some forward-retransmitted packets LOST.
> It does NOT forbid TCP performing further CWR on new losses. A potential
> follow-up patch under preparation is to perform another CWR on "new"
> losses such as
> 1) sequence above high_seq is lost (by resetting high_seq to snd_nxt)
> 2) retransmission is lost.
> 
> Signed-off-by: Yuchung Cheng <ycheng@google.com>

Applied.

      reply	other threads:[~2012-01-22 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20  0:42 [PATCH v2] tcp: detect loss above high_seq in recovery Yuchung Cheng
2012-01-22 19:24 ` 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=20120122.142416.403336311074678485.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=nanditad@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycheng@google.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).