From owner-freebsd-net@FreeBSD.ORG Tue Feb 12 13:30:12 2013 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C01F9215 for ; Tue, 12 Feb 2013 13:30:12 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 34DD0F50 for ; Tue, 12 Feb 2013 13:30:12 +0000 (UTC) Received: (qmail 36993 invoked from network); 12 Feb 2013 14:47:44 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Feb 2013 14:47:44 -0000 Message-ID: <511A43DB.8030400@freebsd.org> Date: Tue, 12 Feb 2013 14:30:03 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrey Zonov Subject: Re: [PATCH] Add a new TCP_IGNOREIDLE socket option References: <201301221511.02496.jhb@freebsd.org> <50FF06AD.402@networx.ch> <061B4EA5-6A93-48A0-A269-C2C3A3C7E77C@lakerest.net> <201302060746.43736.jhb@freebsd.org> <511292C9.4040307@mu.org> <51166019.9040104@mu.org> <51177818.2090900@FreeBSD.org> <5118D375.5000501@freebsd.org> <511A1FA9.1040606@FreeBSD.org> In-Reply-To: <511A1FA9.1040606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: John Baldwin , Alfred Perlstein , Randall Stewart , Kevin Oberman , net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 13:30:12 -0000 On 12.02.2013 11:55, Andrey Zonov wrote: > On 2/11/13 3:18 PM, Andre Oppermann wrote: >> >> Smaller RTO (1s) has become a RFC so there was very broad consensus in >> TCPM that is a good thing. We don't have it yet because we were not fully >> compliant in one case (loss of first segment). I've fixed that a while >> back and will bring 1s RTO soon to HEAD. >> > > They use 300ms at least for me/my link/ISP/etc. Let me be more precise: An initial RTO of 1s was published as RFC. This is what I'm referring to. It affects the setup phase of a connection. A separate issue is the minimum RTO during a connection. According to the RFC the RTO during the lifetime of the connection should also not be less than 1s. The RTO being determined based on the RTT measurement done using timestamps or Karn's algorithm. However on fast links this has been shown to be too long to wait for. So FreeBSD decreased the allowed lower bound to hz/33. This is only effective if your RTO was actually calculated to be equal or lower than that. The result is a quicker re-probing and discovery of the current line conditions. Since the RTO was measured to be less-equal than hz/33, the possible negative downside is very limited. -- Andre