linux-kernel - Re: [PATCH] tcp: Expose the initial RTO via a new sysctl.

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] [day] [month] [year] [list]

Date:	Tue, 31 May 2011 17:43:25 +0200
From:	Hagen Paul Pfeifer <hagen@...u.net>
To:	tsuna <tsunanet@...il.com>
Cc:	"H.K. Jerry Chu" <hkjerry.chu@...il.com>,
	David Miller <davem@...emloft.net>, <kuznet@....inr.ac.ru>,
	<pekkas@...core.fi>, <jmorris@...ei.org>,
	<yoshfuji@...ux-ipv6.org>, <kaber@...sh.net>,
	<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl.

On Tue, 31 May 2011 08:28:18 -0700, tsuna <tsunanet@...il.com> wrote:

> Sorry I meant a knob such as /proc/sys/net/ipv4/tcp_initrto.

That's the same! ;-)

>> The initRTO is the ideal candidate for a
>> per route knob. And happily you will solve 2) with the per route thing
>> too!
> 
> You still need a knob for the default system-wide value, don't you?

Yes, try to re-read the emails. Sysctl is a no-go, with a per route
interface you have the ability to tune the values. Talk with Jerry once
again - he wrote that at Google they already have a patch for this. And
with a per route knob you can select a even smaller value for your local
network (e.g. datacenter) and a larger value for all other routes. It makes
sense to provide a knob for this on a route basis, not on a global sysctl
basis.

But once again: talk with Jerry - he has the expert knowledge!

Hagen
--
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/