netdev - Re: TCP default congestion control in linux should be newreno

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]

Date:	Thu, 4 Dec 2008 21:05:37 +0100
From:	"Saverio Mascolo" <saverio.mascolo@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	ldecicco@...il.com, ilpo.jarvinen@...sinki.fi,
	netdev@...r.kernel.org
Subject: Re: TCP default congestion control in linux should be newreno

>
> The bigger problem is that windows are so much larger now that going
> back to the stone ages and newreno recovery behavior is absolutely not
> an option any more.

average window cannot be much larger, because average windows  follow
network capacity in any case. so you can end up having only more
oscillating windows (i.e. more timeouts, more retransmissions)

>
> So "go back to newreno" is not a suggestion to be taken seriously.

this should be supported by experiments. i do not think reno is stone
age, i think is very close to the optimal you can get given the
feedback available in current nets.

you should show less timeouts, less retransmissions larger goodput
when using a rocket tcp.

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