From: Dan McDonald <danmcd@nexenta.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: Hsiao-keng Jerry Chu <hkchu@google.com>,
bloat-devel@lists.bufferbloat.net
Subject: Re: tcp fast open?
Date: Mon, 20 Feb 2012 16:40:07 -0500 [thread overview]
Message-ID: <20120220214007.GG7049@everywhere.kebe.com> (raw)
In-Reply-To: <CAK6E8=cmr8jH+VX+HGiaDCQxMZVFofFEY_dXt9m6-bzc_Z1Gdw@mail.gmail.com>
On Fri, Feb 17, 2012 at 07:24:32AM -0800, Yuchung Cheng wrote:
<SNIP!>
> 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.
Do you have a paper spec (Internet Draft or other such documentation) so
other platforms can port this?
Thanks,
Dan
next prev parent reply other threads:[~2012-02-20 21:40 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
2012-02-20 21:40 ` Dan McDonald [this message]
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=20120220214007.GG7049@everywhere.kebe.com \
--to=danmcd@nexenta.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=hkchu@google.com \
--cc=ycheng@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