From: David Miller <davem@davemloft.net>
To: kennetkl@ifi.uio.no
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: use SACK RTTs for CC
Date: Sat, 31 Jan 2015 17:26:01 -0800 (PST) [thread overview]
Message-ID: <20150131.172601.384724758739744851.davem@davemloft.net> (raw)
In-Reply-To: <1422558483-6168-1-git-send-email-kennetkl@ifi.uio.no>
From: Kenneth Klette Jonassen <kennetkl@ifi.uio.no>
Date: Thu, 29 Jan 2015 20:08:03 +0100
> Current behavior only passes RTTs from sequentially acked data to CC.
>
> If sender gets a combined ACK for segment 1 and SACK for segment 3, then the
> computed RTT for CC is the time between sending segment 1 and receiving SACK
> for segment 3.
>
> Pass the minimum computed RTT from any acked data to CC, i.e. time between
> sending segment 3 and receiving SACK for segment 3.
>
> Signed-off-by: Kenneth Klette Jonassen <kennetkl@ifi.uio.no>
Applied, thanks.
prev parent reply other threads:[~2015-02-01 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 19:08 [PATCH net-next] tcp: use SACK RTTs for CC Kenneth Klette Jonassen
2015-01-30 17:21 ` Yuchung Cheng
2015-01-30 17:47 ` Yuchung Cheng
2015-02-01 1:26 ` 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=20150131.172601.384724758739744851.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kennetkl@ifi.uio.no \
--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;
as well as URLs for NNTP newsgroup(s).