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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 29 Oct 2014 15:06:24 -0400 (EDT) From: David Miller <davem@...emloft.net> To: eric.dumazet@...il.com Cc: netdev@...r.kernel.org, wygivan@...gle.com Subject: Re: [PATCH net-next] tcp: allow for bigger reordering level From: Eric Dumazet <eric.dumazet@...il.com> Date: Mon, 27 Oct 2014 21:45:24 -0700 > From: Eric Dumazet <edumazet@...gle.com> > > While testing upcoming Yaogong patch (converting out of order queue > into an RB tree), I hit the max reordering level of linux TCP stack. > > Reordering level was limited to 127 for no good reason, and some > network setups [1] can easily reach this limit and get limited > throughput. > > Allow a new max limit of 300, and add a sysctl to allow admins to even > allow bigger (or lower) values if needed. > > [1] Aggregation of links, per packet load balancing, fabrics not doing > deep packet inspections, alternative TCP congestion modules... > > Signed-off-by: Eric Dumazet <edumazet@...gle.com> I'll apply this, thanks. However in the longer term I'd say that this value, if it is to have a limit, then such a limit should probably be scaled based upon the window size. -- 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
Powered by blists - more mailing lists