From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id AAA2521F17F for ; Fri, 4 Jan 2013 20:05:03 -0800 (PST) Received: by mail-ie0-f171.google.com with SMTP id 17so20559576iea.16 for ; Fri, 04 Jan 2013 20:05:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tIMSi0HXfVX5YO3k4wAfmcYTiFlLK8DOwyv3V8XxPsU=; b=G2scrH5TCcdrC9njxu1T+/UIq6O/ODUrYuXt9G5OkMcdDRV3JtxucVK/3/D4S8YvSh SCV8r3uvNW76jsfvHPMo5Vx2XhS/a/nA332PTKaMj66PIw338DM51fPjfAxpsOgQeH3q f0afg1DdDp3GrUP5XgerruZh8r1Z7J66aMpiWm/NYuMcLXjSvJcZWH1ZPtUzTZoekDPH CD9bv9+Ernj5sFblRY4Em8IYmUp02T8Gu/+J/wlOE94qtJ9nG3JgaYKpfnueQvpaMo3M L1pektEQ8e1exDAub4BjB9XT6PurlxRfOyDxnQRQUFu2qZo4vBeZxbNxHDwD/X8m9k86 IWWQ== MIME-Version: 1.0 Received: by 10.50.196.164 with SMTP id in4mr538395igc.86.1357358702986; Fri, 04 Jan 2013 20:05:02 -0800 (PST) Received: by 10.64.135.39 with HTTP; Fri, 4 Jan 2013 20:05:02 -0800 (PST) In-Reply-To: References: Date: Fri, 4 Jan 2013 20:05:02 -0800 Message-ID: From: Dave Taht To: Ketan Kulkarni Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Jerry Chu , Eric Dumazet , Yuchung Cheng , cerowrt-devel Subject: Re: [Cerowrt-devel] TFO crashes cerowrt 3.7.1-1 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2013 04:05:03 -0000 On Fri, Jan 4, 2013 at 7:35 PM, Dave Taht wrote: > It's rather fun to explore a new protocol on a friday night!, but this > thread is getting out of hand. I created a bug for it here: > > https://www.bufferbloat.net/issues/418 > > I don't mind if we continue to discuss it here, but do put packet > captures on the bug, please... > > I scripted up a few tests that hopefully duplicate what ketan was > trying to do. (ketan?) and put up packet captures of the succesful > tests to an x86_64 box I had handy.... > > I will put a sacrificial cerowrt box back up with a serial port on it > before sunday.... > > I noted in the bug above (with more detail) > > On a x86_64 path over a 4 hop wifi mesh network, httpping using polipo > as a proxy not only "worked", but roughly halved the time taken by a > ~40kbyte http GET. > > Typical httpping result, polipo, no TFO > > connected to 172.26.3.4:80 (274 bytes), seq=3D4 time=3D10.76 ms > > Typical result, polipo, useTCPFastopen =3D true in it's config and > /proc/sys/net/ipv4/tcp_fastopen =3D 3 on both sides.... > > connected to 172.26.3.4:80 (274 bytes), seq=3D4 time=3D6.61 ms > > Impressive! > > If the security issues with the idea are resolved (I'm aware of the > prior effort to do this but haven't thought deeply about how TFO > attempts to resolve those issues), and TFO can be deployed, it will be > a win for a wide range of latency sensitive tcp traffic types. Spoke WAY too soon on the performance front, looks like we get a RST from one of the (3.6.11) middleboxes in that testbed before we get the whole file. put up a new capture on https://www.bufferbloat.net/issues/418 Calling it a night. > > > -- > Dave T=E4ht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html