From: Yuchung Cheng <ycheng@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Hsiao-keng Jerry Chu <hkchu@google.com>,
bloat-devel@lists.bufferbloat.net
Subject: Re: tcp fast open?
Date: Fri, 17 Feb 2012 07:24:32 -0800 [thread overview]
Message-ID: <CAK6E8=cmr8jH+VX+HGiaDCQxMZVFofFEY_dXt9m6-bzc_Z1Gdw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6JLyDZadqBWOh1jg3jZ8=eZbyf-Zsz_YLVQBogeqvVdQ@mail.gmail.com>
On Fri, Feb 17, 2012 at 6:38 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I am curious if working code exists for tcp fast open for Linux as yet?
>
> I just finished slamming an implementation of tcp-ledbat v9 into
> cerowrt (untested as yet, ledbat vs sfqred
> will be interesting), and based on the presentation at the last linux
> plumbers conference, tcp fast open looked interesting too.
>
>
Hi Dave,
At this moment, we do have a working patch under testing it
internally. The handshake code is the most complicated and critical
piece in TCP. One important test is the fail over if routers drop or
act weirdly on SYN/SYN-ACK with payload and/or experimental TCP
options. If things go well we will upstream it to Linux netdev in
April and I'll CC you.
Btw, I am very interested in learning the result of AQM vs
delayed-based CC like ledbat.
Cheers,
Yuchung
next prev parent reply other threads:[~2012-02-17 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 14:38 Dave Taht
2012-02-17 15:24 ` Yuchung Cheng [this message]
2012-02-20 21:40 ` Dan McDonald
2012-02-21 7:30 ` Jerry Chu
2012-02-21 18:25 ` Rick Jones
2012-02-23 18:20 ` Justin McCann
2012-02-20 22:55 ` Juliusz Chroboczek
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK6E8=cmr8jH+VX+HGiaDCQxMZVFofFEY_dXt9m6-bzc_Z1Gdw@mail.gmail.com' \
--to=ycheng@google.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=hkchu@google.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