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
| ||
|
Message-Id: <F7D530D6-304E-4B99-8143-9E197AF8D74E@simula.no> Date: Thu, 29 Oct 2009 14:50:48 +0100 From: Andreas Petlund <apetlund@...ula.no> To: William Allen Simpson <william.allen.simpson@...il.com> Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, shemminger@...tta.com, ilpo.jarvinen@...sinki.fi, davem@...emloft.net Subject: Re: [PATCH 2/3] net: TCP thin linear timeouts Den 28. okt. 2009 kl. 04.20 skrev William Allen Simpson: > Sorry to be too picky about the naming, but "rm_expb" really doesn't > mean what is actually done. Perhaps TCP_THIN_LINEAR_BACKOFF and > sysctl_tcp_thin_linear_backoff? > I agree that the name should be changed. As it represents linear timeouts and does not back off exponentially, I suggest TCP_THIN_LINEAR_TIMEOUTS and sysctl_tcp_thin_linear_timeouts. > Also, as debated on some other recent patches, shouldn't the global > sysctl specify the default, and the per socket option specify the > forced override? The rationale behind the suggested model is to allow the modifications to be forced active in cases where the application that generates the thin stream is proprietary, legacy, or that the code for other reasons can not be modified (as is the case, for instance, for many game clients). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists