From: Ketan Kulkarni <ketkulka@gmail.com>
To: Dave Taht <dave.taht@gmail.com>, Eric Dumazet <eric.dumazet@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] TCP TFO client behaviour
Date: Wed, 12 Dec 2012 14:31:13 +0530 [thread overview]
Message-ID: <CAD6NSj78ZRXZ50eJKAjAoJ-Wy_Na3=v+DqoE0V=Qqcit_nPtNw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Rojac6KiS_zcCDwTQET_yZvhT9NujZqev4jA0x3iBAw@mail.gmail.com>
On Tue, Dec 11, 2012 at 11:22 PM, Dave Taht <dave.taht@gmail.com> 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äht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-12-12 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 16:48 Ketan Kulkarni
2012-12-11 16:59 ` Eric Dumazet
2012-12-11 17:52 ` Dave Taht
2012-12-11 18:41 ` Rick Jones
2012-12-11 20:00 ` Dave Taht
2012-12-11 20:52 ` Rick Jones
2012-12-12 9:01 ` Ketan Kulkarni [this message]
2012-12-12 19:17 ` Jan Ceuleers
2012-12-12 10:45 ` Eggert, Lars
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD6NSj78ZRXZ50eJKAjAoJ-Wy_Na3=v+DqoE0V=Qqcit_nPtNw@mail.gmail.com' \
--to=ketkulka@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=eric.dumazet@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox