From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756782Ab1EaPZ0 (ORCPT ); Tue, 31 May 2011 11:25:26 -0400 Received: from alternativer.internetendpunkt.de ([88.198.24.89]:42154 "EHLO geheimer.internetendpunkt.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752827Ab1EaPZY (ORCPT ); Tue, 31 May 2011 11:25:24 -0400 To: tsuna Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 31 May 2011 17:25:22 +0200 From: Hagen Paul Pfeifer Cc: "H.K. Jerry Chu" , David Miller , , , , , , , In-Reply-To: References: <1305715384-81716-1-git-send-email-tsunanet@gmail.com> <20110518.152653.1486764697527722925.davem@davemloft.net> <20110518.155200.801089483916944725.davem@davemloft.net> <20110518202025.GC4175@nuttenaction> Message-ID: User-Agent: RoundCube Webmail/0.1-rc1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 31 May 2011 07:48:09 -0700, tsuna wrote: > I talked to Jerry and he's agreed to share some patches that Google > has been using internally for years. Great! > Personally what I think would be ideal would be: > 1. A sysctl knob for initRTO, to allow people to adjust this > appropriately for their environment. > 2. Apply the srtt / rttvar seen on previous connections to new > connections. > > Does that sound reasonable? > > For 2), I'm not sure how the details would work yet, I believe the > kernel already has what's necessary to remember these things on a per > peer basis, but it would be nice if I could specify things like "for > 10.x.0.0/16 (local datacenter) use this aggressive setting, for > 10.0.0.0/8 (my internal backend network) use that, for everything else > (Internets etc.) use the default". Skip sysctl, it is deprecated. The initRTO is the ideal candidate for a per route knob. And happily you will solve 2) with the per route thing too! ;-) Search the web, you will find some patches where you can see how to extend the per route system - including iproute2. Hagen From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hagen Paul Pfeifer Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl. Date: Tue, 31 May 2011 17:25:22 +0200 Message-ID: References: <1305715384-81716-1-git-send-email-tsunanet@gmail.com> <20110518.152653.1486764697527722925.davem@davemloft.net> <20110518.155200.801089483916944725.davem@davemloft.net> <20110518202025.GC4175@nuttenaction> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "H.K. Jerry Chu" , David Miller , , , , , , , To: tsuna Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 31 May 2011 07:48:09 -0700, tsuna wrote: > I talked to Jerry and he's agreed to share some patches that Google > has been using internally for years. Great! > Personally what I think would be ideal would be: > 1. A sysctl knob for initRTO, to allow people to adjust this > appropriately for their environment. > 2. Apply the srtt / rttvar seen on previous connections to new > connections. > > Does that sound reasonable? > > For 2), I'm not sure how the details would work yet, I believe the > kernel already has what's necessary to remember these things on a per > peer basis, but it would be nice if I could specify things like "for > 10.x.0.0/16 (local datacenter) use this aggressive setting, for > 10.0.0.0/8 (my internal backend network) use that, for everything else > (Internets etc.) use the default". Skip sysctl, it is deprecated. The initRTO is the ideal candidate for a per route knob. And happily you will solve 2) with the per route thing too! ;-) Search the web, you will find some patches where you can see how to extend the per route system - including iproute2. Hagen