From: Gavin McCullagh <Gavin.McCullagh@nuim.ie>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>, Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH/RFC] [v3] TCP: use non-delayed ACK for congestion control RTT
Date: Sun, 30 Dec 2007 12:35:04 +0000 [thread overview]
Message-ID: <20071230123504.GB23931@nuim.ie> (raw)
In-Reply-To: <Pine.LNX.4.64.0712301139150.31698@kivilampi-30.cs.helsinki.fi>
On Sun, 30 Dec 2007, Ilpo Järvinen wrote:
> I guess the non-minimum TSO delays are only significant in case there was
> something unexpectional happening and in such case we definately want to
> have some measurements taken.
Broadly speaking, delay-based schemes need as much information about the
queueing delay as possible so more points are generally useful,
particularly if the delay is fluctuating rapidly.
When we started looking at delay-based schemes we had trouble with delay
information fluctuating wildly due to TSO. John Heffner made a change
(that I can't find at the minute) which reduced a TSO timeout and seemed to
reduce this problem greatly. It's worth bearing in mind though that TSO
may cause spuriously high delay measurements.
Gavin
prev parent reply other threads:[~2007-12-30 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 13:44 [PATCH/RFC] TCP: use non-delayed ACK for congestion control RTT Gavin McCullagh
2007-12-18 20:40 ` [PATCH/RFC] [v2] " Gavin McCullagh
2007-12-19 10:28 ` Gavin McCullagh
2007-12-19 11:08 ` Ilpo Järvinen
2007-12-19 11:31 ` Gavin McCullagh
2007-12-19 13:30 ` Ilpo Järvinen
2007-12-21 11:14 ` David Miller
2007-12-21 13:31 ` Gavin McCullagh
2007-12-21 14:05 ` David Miller
2007-12-21 14:07 ` Ilpo Järvinen
2007-12-21 14:10 ` Ilpo Järvinen
2007-12-30 1:15 ` [PATCH/RFC] [v3] " Gavin McCullagh
2007-12-30 1:25 ` Gavin McCullagh
2007-12-30 3:09 ` David Miller
2007-12-30 12:20 ` Gavin McCullagh
2007-12-30 3:06 ` David Miller
2007-12-30 9:43 ` Ilpo Järvinen
2007-12-30 12:35 ` Gavin McCullagh [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=20071230123504.GB23931@nuim.ie \
--to=gavin.mccullagh@nuim.ie \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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).