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
| ||
|
Date: Mon, 21 Nov 2016 13:20:33 -0500 (EST) From: David Miller <davem@...emloft.net> To: fw@...len.de Cc: netdev@...r.kernel.org Subject: Re: [PATCH v2 next 0/2] tcp: make undo_cwnd mandatory for congestion modules From: Florian Westphal <fw@...len.de> Date: Mon, 21 Nov 2016 14:18:36 +0100 > highspeed, illinois, scalable, veno and yeah congestion control algorithms > don't provide a 'cwnd_undo' function. This makes the stack default to a > 'reno undo' which doubles cwnd. However, the ssthresh implementation of > these algorithms do not halve the slowstart threshold. This causes similar > issue as the one fixed for dctcp in ce6dd23329b1e ("dctcp: avoid bogus > doubling of cwnd after loss"). > > In light of this it seems better to remove the fallback and make undo_cwnd > mandatory. > > First patch fixes those spots where reno undo seems incorrect by providing > .cwnd_undo functions, second patch removes the fallback. Series applied, thanks for following up on this.
Powered by blists - more mailing lists