| 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: Fri, 28 Oct 2011 14:53:29 -0700 From: Andy Lutomirski <luto@...capital.net> To: Daniel Baluta <dbaluta@...acom.com> Cc: davem@...emloft.net, eric.dumazet@...il.com, kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net, netdev@...r.kernel.org, rick.jones2@...com Subject: Re: [RFC v2] tcp: Export TCP Delayed ACK parameters to user On Fri, Oct 28, 2011 at 2:14 PM, Daniel Baluta <dbaluta@...acom.com> wrote: > RFC2581 ($4.2) specifies when an ACK should be generated as follows: > > " .. an ACK SHOULD be generated for at least every second > full-sized segment, and MUST be generated within 500 ms > of the arrival of the first unacknowledged packet. > " > > We export the number of segments and the timeout limits > specified above, so that a user can tune them according > to its needs. > > Specifically: > * /proc/sys/net/ipv4/tcp_delack_segs, represents > the threshold for the number of segments. > * /proc/sys/net/ipv4/tcp_delack_min, specifies > the minimum timeout value > * /proc/sys/net/ipv4/tcp_delack_max, specifies > the maximum timeout value. This is neat, but IMO it should be per socket -- I (and possibly most other people who would use it) want to do this kind of tuning per flow, not per-route or per-interface. --Andy -- 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