Hi David, I ran couple of testing to see the limited slow start for HSTCP. For this testing, I set max_ssthresh value to 100. With the slow start, it takes around 4sec to hit the cwnd of 21862 (more than 6000 packet drops for one rtt). With the limited slow start, it takes 108sec to hit the cwnd of 8420. If taken into account a delayed ack, it looks fine for me.
See the plots below. With Slow Start: http://netsrv.csc.ncsu.edu/net-2.6.22/slow_start/600--HSTCP-HSTCP-NONE--400-3-1.0--1000-120-0-0-1-1-5-500--1.0-0.2-133000-73-3000000-0.93-150--1/ With Limited Slow Start: http://netsrv.csc.ncsu.edu/net-2.6.22/limited_slow_start/600--HSTCP-HSTCP-NONE--400-3-1.0--1000-120-0-0-1-1-5-500--1.0-0.2-133000-73-3000000-0.93-150--1/ Thanks, Sangtae On 5/3/07, David Miller <[EMAIL PROTECTED]> wrote:
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> Date: Thu, 3 May 2007 15:34:25 +0300 (EEST) > Reuse limited slow-start (RFC3742) included into tcp_cong instead > of having another implementation in High Speed TCP. > > Compile tested only. > > Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]> Thanks for noticing this code duplication. I've applied this, but it would be great if someone would do some sanity tests of highspeed to make sure it's ok. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
