From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 13:08:01 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDB4A1065679 for ; Thu, 2 Dec 2010 13:08:01 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 702EA8FC0C for ; Thu, 2 Dec 2010 13:08:01 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PO8tB-00057g-Vq for freebsd-current@freebsd.org; Thu, 02 Dec 2010 14:07:57 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Dec 2010 14:07:57 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Dec 2010 14:07:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 02 Dec 2010 14:07:59 +0100 Lines: 23 Message-ID: References: <4CDD0A71.7020708@freebsd.org> <4CF788D7.8020905@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <4CF788D7.8020905@freebsd.org> X-Enigmail-Version: 1.1.2 Subject: Re: [HEADS UP] Significant TCP work committed to head - CUBIC & H-TCP committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2010 13:08:01 -0000 On 12/02/10 12:53, Lawrence Stewart wrote: > For the really interested (by now I suspect my audience is down to 0, > but still), you might want to load siftr and enable/disable it during > each test run and make your very own plot of cwnd vs time to see what's > really going on behind the scenes. > > Ok that's enough for now, but much more is on the way. Please let me > know if you have any feedback or run into any problems related to this work. Hi, My question isn't very constructive but I'd like to know more about this topic. Have you seen this: http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html http://developers.slashdot.org/story/10/11/26/1729218/Google-Microsoft-Cheat-On-Slow-Start-mdash-Should-You ? In short: is the existance of slow-start a property of (New)Reno and will some of the new algorithms make it less "cautious", i.e. faster? I don't think it's critical but I'm often noticing it, especially on bulk transfers over LAN.