From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (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 053B221F1B0; Wed, 12 Dec 2012 01:01:13 -0800 (PST) Received: by mail-ie0-f169.google.com with SMTP id c14so1313161ieb.14 for ; Wed, 12 Dec 2012 01:01:13 -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=coW8XaQmrTS4Fn1Z8pXWkUYC2gGBhUI9b3nLMu1eU8g=; b=cjgCGcJ/y8wp7lC4GlHp7viojgNRo5opomiUddF4o3BNAfzJF4QEubCZgzsx3YBlTP l00Vhahedh+4tWu9Vb5RiEKjGOf9nTL4DNPKcbpqGMRBvybIxqBoP40l4iW6qYdw9X3I G1e9Lyq2p7VKvQ0YYHBPdil5ObJgYRSE96P+9rmlbvNLmdzvi0TlIgf/KzPtypqNtaGB 9bhSO27Xc4dCnX8baz7ME1YzESRvKc4TAy4U5nwxnL2jO3MWUbwZxfvwrXSrRSsd0knc VhzVnWEqySEB/keExG6nAh1stOQCRBHr3mFZGq1YSGRdkvQJRhTHSIx3KX9I2a3Ebk1J gw8w== MIME-Version: 1.0 Received: by 10.50.41.200 with SMTP id h8mr12920867igl.0.1355302873485; Wed, 12 Dec 2012 01:01:13 -0800 (PST) Received: by 10.64.53.105 with HTTP; Wed, 12 Dec 2012 01:01:13 -0800 (PST) In-Reply-To: References: <1355245195.27891.108.camel@edumazet-glaptop> Date: Wed, 12 Dec 2012 14:31:13 +0530 Message-ID: From: Ketan Kulkarni To: Dave Taht , Eric Dumazet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: cerowrt-devel@lists.bufferbloat.net, bloat Subject: Re: [Cerowrt-devel] [Bloat] TCP TFO client behaviour 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: Wed, 12 Dec 2012 09:01:14 -0000 On Tue, Dec 11, 2012 at 11:22 PM, Dave Taht wrote: >> >> I really wonder why this is sent to these lists instead of netdev ? > > In my case I find it impossible to read netdev on a regular basis, > with the size of the traffic and the unbelievable patch burden - (not > that I can't filter it, but that fairly often I find a patch too > tempting to not apply and then play with) > > I have no problem taking a conversation to netdev if needed... > Well, I have opened a thread on netdev as well. > However I'd note that TCP fast open is not just a linux feature, but > affects the entire internet. Perhaps the readership here has a more > broad view of how this should be approached. > First, I would really like to get wider views about this. My only concern is - If syn+data is sent by client and syn-ack only acks the ISN, then isnt this a sufficient indication that server now is not supporting the TFO? So for further connections to this server instead of sending syn+data, only ask for cookie. (fall back to the state where it was all started) (Note that this condition is different from syn+data is dropped in the nw.) Yuchung might be right in saying it doesn't lead to any performance penalty, however sending syn+data to a server seems a little odd when we know we have sufficient information to believe that it may not be accepted at first, retransmitted later. And otherwise we also have a way to fall back and re-attempt the TFO. If you guys still insist, I can stop here and continue on netdev. > Ketan has been busily adding support for TFO to a couple tools used in > cerowrt. (httping is already out there in a release!) > > It's my hope to be able to sanely test it in cerowrt's 3.7.x release. > > I also am concerned about TFO wider adoption into other tools like > these (ssh? dns?) and what those effects might be. > > I'm probably dropping the syn optimization in simple_qos.sh because of > tcp fast open. But I would prefer to gather data and test, first, with > good tools. Are there any other tools besides chrome and httpping > setup for clients? > > I look forward to trying out the polipo support. > >> >> >> _______________________________________________ >> Bloat mailing list >> Bloat@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat > > > > -- > Dave T=E4ht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html