From: Stephen Hemminger <shemminger@vyatta.com>
To: "Injong Rhee" <rhee@ncsu.edu>
Cc: "Injong Rhee" <rhee@eos.ncsu.edu>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] CUBIC v2.3 with new improved slow start
Date: Wed, 29 Oct 2008 16:40:45 -0700 [thread overview]
Message-ID: <20081029164045.7422b68d@extreme> (raw)
In-Reply-To: <000b01c93a1c$090222c0$6c01a8c0@RHEELAPTOP>
On Wed, 29 Oct 2008 19:14:03 -0400
"Injong Rhee" <rhee@ncsu.edu> wrote:
> >
> > This looks like a good optimization, it obviously needs more testing
> > because Linux always seems to find new broken hardware. The areas
> > that need to be tested should include:
> > * MacOs has a broken version of delayed ack that might cause
> > HyStart to radically underestimate.
>
> We tested with FreeBSD. I presume that it covers MacOS. We will look into
> that.
No Darwin added some stupid code that holds off acks for up to 2 seconds.
> > * Applications that dribble out packets might get better (or
> > worse) performance. This include dumb web servers.
>
> Not really. It does not affect those flows that do not use their full
> capacity of the network. HyStart kicks in only when the flow are using more
> than avail bw during slow start. If the applications do not pump data in, it
> would still be in slow start -- while in slow start, HyStart works like the
> traditional slow start (double cwnd per rtt).
>
> > * Does this increase or reduce latency when using TCP for
> > applications which never fill the congestion window? (games, financial,
> > etc).
> >
>
> For the same reasons as above, No, HyStart does not engage in this
> situation.
>
Ok
next prev parent reply other threads:[~2008-10-29 23:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 21:28 [PATCH] CUBIC v2.3 with new improved slow start Injong Rhee
2008-10-29 22:39 ` Stephen Hemminger
2008-10-29 23:14 ` Injong Rhee
2008-10-29 23:40 ` Stephen Hemminger [this message]
2008-10-29 23:53 ` Rick Jones
2008-10-30 0:54 ` Injong Rhee
2008-10-30 1:08 ` Rick Jones
2008-10-29 23:45 ` David Miller
2008-10-30 15:36 ` [PATCH] tcp: mark BIC as experimental Stephen Hemminger
2008-10-31 7:50 ` David Miller
2008-10-31 16:41 ` Stephen Hemminger
2008-10-31 19:04 ` David Miller
2008-10-31 19:16 ` [RFC] tcp: make H-TCP the default congestion control Stephen Hemminger
2008-10-31 19:43 ` Sangtae Ha
2008-10-31 20:02 ` rhee
2008-11-02 4:29 ` David Miller
2008-11-02 7:27 ` [PATCH] CUBIC v2.3 with new improved slow start David Miller
2008-11-03 22:19 ` Sangtae Ha
2008-11-03 22:49 ` Stephen Hemminger
2008-11-04 1:12 ` 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=20081029164045.7422b68d@extreme \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.org \
--cc=rhee@eos.ncsu.edu \
--cc=rhee@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).