Netdev List
 help / color / mirror / Atom feed
From: "Injong Rhee" <rhee@eos.ncsu.edu>
To: "Stephen Hemminger" <shemminger@osdl.org>, "Sangtae Ha" <sha2@ncsu.edu>
Cc: <netdev@vger.kernel.org>
Subject: Re: TCP congestion graphs
Date: Wed, 25 Oct 2006 18:34:17 -0400	[thread overview]
Message-ID: <000701c6f885$b57aa390$4a580e98@ncsu2cc0c3fa00> (raw)
In-Reply-To: 20061025110207.78d38779@freekitty

Not sure why the slow start for cubic is slower than the others.
We will check on this.

----- Original Message ----- 
From: "Stephen Hemminger" <shemminger@osdl.org>
To: "Douglas Leith" <doug.leith@nuim.ie>; "Sangtae Ha" <sha2@ncsu.edu>
Cc: <netdev@vger.kernel.org>
Sent: Wednesday, October 25, 2006 2:02 PM
Subject: TCP congestion graphs


>I ran some congestion window tests against 2.6.19-rc3.
> For congestion window graphs see:
> http://developer.osdl.org/shemminger/tcp/2.6.19-rc3/
> 
> The connection was a single flow with a 500ms RTT and a 
> 100Mbit slowest link speed.
> 
> BIC  OK
> CUBIC OK (after patch)
> HIGHSPEED BROKEN?
> HTCP OK
> RENO OK (massive overshoot)
> SCALEABLE OK
> VEGAS OK (no better than Reno)
> VENO Same as Reno?
> WESTWOOD Overshoot then low window
> 
> Highspeed has something wrong (test glitch?)
> Westwood behaves poorly
> Veno seems no better than either Reno or Vegas in this
> case.
> 
> The end systems were from latest git. The netem bridge is using
> 2.6.18-rt with a patch to netem to use hrtimers.  iperf was modified
> to allow easy selection of congestion control.
> 
> -- 
> Stephen Hemminger <shemminger@osdl.org>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2006-10-25 22:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 18:02 TCP congestion graphs Stephen Hemminger
2006-10-25 22:34 ` Injong Rhee [this message]
2006-10-26  1:30   ` Stephen Hemminger
2006-10-26 18:50     ` Hagen Paul Pfeifer
2006-10-26 19:36       ` Stephen Hemminger
2006-10-31 20:00   ` TCP congestion graphs (2.6.19-rc4) Stephen Hemminger
2006-10-31 23:25     ` Xiaoliang (David) Wei
2006-11-01  0:10       ` Stephen Hemminger
2006-11-01  1:30         ` David Miller
2006-11-01  5:25           ` Evgeniy Polyakov
2006-11-01  5:58             ` Stephen Hemminger
2006-11-02  5:44               ` David Miller
2006-11-02 19:58                 ` Stephen Hemminger
2006-11-28 22:38           ` 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='000701c6f885$b57aa390$4a580e98@ncsu2cc0c3fa00' \
    --to=rhee@eos.ncsu.edu \
    --cc=netdev@vger.kernel.org \
    --cc=sha2@ncsu.edu \
    --cc=shemminger@osdl.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