From: "Injong Rhee" <rhee@ncsu.edu>
To: "Rick Jones" <rick.jones2@hp.com>,
"Stephen Hemminger" <shemminger@vyatta.com>
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 20:54:04 -0400 [thread overview]
Message-ID: <001d01c93a2a$023f2560$6c01a8c0@RHEELAPTOP> (raw)
In-Reply-To: 4908F775.9040504@hp.com
In any situation where delayed acks screw things up, HyStart would work
exactly like the old slow start. No harm is done. Since those long delayed
acks are simply filtered out, HyStart would not detect the exit points
correctly -- in this particular case, it would delay the exit point until
packet losses occur. Then this is the behavior of the old slow start.
If some bad implementation causes HyStart to exit from slow start too early
(before the full utilization of the network), then it can be a problem. But
we have not found that case. Even over asymmetric paths, premature exits do
not occur (well based on our own def of premature exits, of course).
----- Original Message -----
From: "Rick Jones" <rick.jones2@hp.com>
To: "Stephen Hemminger" <shemminger@vyatta.com>
Cc: "Injong Rhee" <rhee@ncsu.edu>; "Injong Rhee" <rhee@eos.ncsu.edu>;
<netdev@vger.kernel.org>
Sent: Wednesday, October 29, 2008 7:53 PM
Subject: Re: [PATCH] CUBIC v2.3 with new improved slow start
> Stephen Hemminger wrote:
>> 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.
>
> Is this Apple's reimplementation of the ACK avoidance heuristics in OSX
> they used to have in previous versions of MacOS with the Mentat TCP/IP
> stack?
>
> FWIW, HP-UX and Solaris also have ACK avoidance heursistics - they have a
> Mentat history - although both should be pretty good and neither should
> hold-off ACKs for two seconds...
>
> rick jones
>
next prev parent reply other threads:[~2008-10-30 1:39 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
2008-10-29 23:53 ` Rick Jones
2008-10-30 0:54 ` Injong Rhee [this message]
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='001d01c93a2a$023f2560$6c01a8c0@RHEELAPTOP' \
--to=rhee@ncsu.edu \
--cc=netdev@vger.kernel.org \
--cc=rhee@eos.ncsu.edu \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.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