From: Stephen Hemminger <shemminger@vyatta.com>
To: Lucas Nussbaum <lucas.nussbaum@loria.fr>
Cc: netdev@vger.kernel.org, Sangtae Ha <sha2@ncsu.edu>
Subject: Re: [PATCH] tcp_cubic: enable TCP timestamps
Date: Tue, 8 Mar 2011 10:42:11 -0800 [thread overview]
Message-ID: <20110308104211.3567526f@nehalam> (raw)
In-Reply-To: <20110308080926.GA22641@xanadu.blop.info>
On Tue, 8 Mar 2011 09:09:26 +0100
Lucas Nussbaum <lucas.nussbaum@loria.fr> wrote:
> The Hystart slow start algorithm requires precise RTT delay measurements
> to decide when to leave slow start. However, currently, CUBIC doesn't
> enable TCP timestamps. This can cause Hystart to mis-estimate the RTT,
> and to leave slow start too early, generating bad performance since
> convergence to the optimal cwnd is slower.
>
> Timestamps are already used by TCP Illinois, LP, Vegas, Veno and Yeah.
>
> Signed-off-by: Lucas Nussbaum <lucas.nussbaum@loria.fr>
Just to explain what RTT_STAMP does. It causes the tcp receive code
to compute the rtt using high resolution clocks rather than just
jiffies. It requires access to ktime_get_real which means accessing
clock source. This is cheap for TSC, a little expensive for HPET but
expensive for PIT. I worry that enabling it may hurt regular users
on old desktops. But without it enabling RTT_STAMP, packets that
get acked in less than a jiffie (1 - 10 ms) will
Also I should have used ktime_get rather than ktime_get_real
because real time is altered by NTP and other actions.
next prev parent reply other threads:[~2011-03-08 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 8:09 [PATCH] tcp_cubic: enable TCP timestamps Lucas Nussbaum
2011-03-08 18:42 ` Stephen Hemminger [this message]
2011-03-08 18:55 ` David Miller
2011-03-08 19:15 ` Sangtae Ha
2011-03-08 19:36 ` Lucas Nussbaum
2011-03-08 19:38 ` David Miller
2011-03-08 19:17 ` Stephen Hemminger
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=20110308104211.3567526f@nehalam \
--to=shemminger@vyatta.com \
--cc=lucas.nussbaum@loria.fr \
--cc=netdev@vger.kernel.org \
--cc=sha2@ncsu.edu \
/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).