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: Fri, 20 May 2011 13:00:02 +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: David Miller , , , , , , , , To: "H.K. Jerry Chu" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 20 May 2011 03:27:37 -0700, "H.K. Jerry Chu" wrote: Hi Jerry > Not sure how our various parameter tuning proposals deviate from the "TCP > over everything" principle? For our environment it hurts because we _always_ have an initial RTO >1. I understand and accept that 98% will benefit of this modification, no doubt Jerry! Try to put yourself in our situation: imaging a proposal of an init RTO modification to 0.5 seconds. Maybe because 98% of Internet traffic is now localized and the RTO is average now 0.2 seconds. Anyway, this will penalize your network always and this will be the situation for one of my customer. I can live with that, I see the benefits for the rest of the world. But I am happy to see a knob where I can restore the old behavior. Maybe some other environments will benefit from a even lower or higher initial RTO. Hagen