Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753763Ab1EQLCt (ORCPT ); Tue, 17 May 2011 07:02:49 -0400 Received: from alternativer.internetendpunkt.de ([88.198.24.89]:55403 "EHLO geheimer.internetendpunkt.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753432Ab1EQLCs (ORCPT ); Tue, 17 May 2011 07:02:48 -0400 To: Eric Dumazet 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, 17 May 2011 13:02:47 +0200 From: Hagen Paul Pfeifer Cc: Benoit Sigoure , , , , , , , , In-Reply-To: <1305619677.2850.11.camel@edumazet-laptop> References: <1305618020-72535-1-git-send-email-tsunanet@gmail.com> <1305618020-72535-2-git-send-email-tsunanet@gmail.com> <1305619677.2850.11.camel@edumazet-laptop> 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 Content-Length: 1078 Lines: 26 On Tue, 17 May 2011 10:07:57 +0200, Eric Dumazet wrote: > I wont discuss if introducing a new sysctl is welcomed, only on patch > issues. I believe some work in IETF is done to reduce the 3sec value to > 1sec anyway. Why not? I though all new knobs in this area should be done on a per route metric so it can be controlled on a per path basis. RTO should be adjustable on a per path basis, because it depends on the path. Some months back [1] I posted a patch to enable/disable TCP quick ack mode, which has nothing to do with network paths, just with a local server policy. But David rejected the patch with the argument that I should use a per path knob (this is a little bit inapprehensible for me, but David has the last word). Hagen [1] http://kerneltrap.org/mailarchive/linux-netdev/2010/8/23/6283640 -- 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/