netdev - Re: Why is tcp_reno_min

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 4 Apr 2008 11:31:14 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	"John Heffner" <johnwheffner@...il.com>,
	"Lachlan Andrew" <lachlan.andrew@...il.com>
Cc:	"Xiaoliang David Wei" <davidwei79@...il.com>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: Why is tcp_reno_min_cwnd() ssthresh/2?

> Greetings all,
> 
> Apologies if this is a dumb question, but why does
> tcp_reno_min_cwnd()  return  ssthresh/2?
> 
> Since   ssthresh <- snd_cwnd/2   on loss, this looks like it tries to
> reduce  snd_cwnd  to 1/4 its value before a loss event, presumably
> then slow-starting back to half of the original  snd_cwnd.
> 
> As Tom Quetchenbach pointed out, it is also odd that  omitting
> min_cwnd()  from a congestion control module causes  ssthresh  to be
> used, giving different results from using  tcp_reno_min_cwnd().
> 
> Thanks,
> Lachlan

First sighed 5 years ago, and every times it comes up, the original
behaviour is retained.

http://oss.sgi.com/archives/netdev/2003-01/msg00114.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html