netdev - Re: [PATCH] [TCP] Sysctl: document tcp_max

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <464E1144.4010806@psc.edu>
Date:	Fri, 18 May 2007 16:49:08 -0400
From:	John Heffner <jheffner@....edu>
To:	Rick Jones <rick.jones2@...com>
CC:	Baruch Even <baruch@...en.org>,
	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
	David Miller <davem@...emloft.net>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] [TCP] Sysctl: document tcp_max_ssthresh (Limited	Slow-Start)

Rick Jones wrote:
> as an asside, "tcp_max_ssthresh" sounds like the maximum value ssthresh 
> can take-on.  is that correct, or is this more of a "once ssthresh is 
> above this, behave in this new way?"  If that is the case, while the 

I don't like it either, but you'll have to talk to Sally Floyd about 
that one.. ;)

In general, I would like the documentation to emphasize more how to set 
the parameter than describe the algorithm.  The max_ssthresh parameter 
should ideally be set to the bottleneck queue size, or more 
realistically a conservative value that's likely to be smaller than the 
bottleneck queue size.  When max_ssthresh is smaller than the bottleneck 
queue, (limited) slow start will not overflow it until cwnd has fully 
ramped up to the appropriate size.

   -John
-
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