Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756873Ab1EaOsc (ORCPT ); Tue, 31 May 2011 10:48:32 -0400 Received: from mail-gw0-f46.google.com ([74.125.83.46]:57458 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751265Ab1EaOsa (ORCPT ); Tue, 31 May 2011 10:48:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=H+BKju8paFjRwbzfRC0XTjv20A+P7k5xFyG2UifrpVDzaBssm5QrbbB1ur3pUMiE8s wH0tuVXECtDLe98ZdsD1O8PBcCWrzHYCfTOVLN5ZS3rNmGocIwo3ni8JyO04EbuzJAWq lJXtLFf4AIHdK2WM+zVsfROHbiTxWUoP+q2Xo= MIME-Version: 1.0 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> From: tsuna Date: Tue, 31 May 2011 07:48:09 -0700 Message-ID: Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl. To: "H.K. Jerry Chu" Cc: Hagen Paul Pfeifer , David Miller , kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1835 Lines: 41 On Fri, May 20, 2011 at 5:06 PM, H.K. Jerry Chu wrote: > Yep, that's why we've had a knob for this for years. I was traveling last week so sorry for not replying earlier to various comments people made. I talked to Jerry and he's agreed to share some patches that Google has been using internally for years. I started this work because after leaving Google and taking these changes for granted, I was surprised to find that they weren't actually part of the mainline Linux kernel. It seems that David is willing to accept a change that will lower the initRTO to 1s (compile-time constant), with a fallback to 3s (compile-time constant), as per the draft rfc2988bis. Others are legitimately worried about the impact this would cause in environments where RTT is typically (or always) in the 1-3s range. Some would like to see this as a per-destination thing. 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". -- Benoit "tsuna" Sigoure Software Engineer @ www.StumbleUpon.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/