From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>, Yuchung Cheng <ycheng@google.com>
Cc: davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org,
ncardwell@google.com, sivasankar@cs.ucsd.edu
Subject: Re: [PATCH net-next] tcp: enable sockets to use MSG_FASTOPEN by default
Date: Fri, 01 Nov 2013 08:29:21 -0700 [thread overview]
Message-ID: <5273C8D1.5080608@hp.com> (raw)
In-Reply-To: <1383261598.19864.0.camel@edumazet-glaptop2.roam.corp.google.com>
On 10/31/2013 04:19 PM, Eric Dumazet wrote:
> On Thu, 2013-10-31 at 09:19 -0700, Yuchung Cheng wrote:
>> Applications have started to use Fast Open (e.g., Chrome browser has
>> such an optional flag) and the feature has gone through several
>> generations of kernels since 3.7 with many real network tests. It's
>> time to enable this flag by default for applications to test more
>> conveniently and extensively.
>>
>> Signed-off-by: Yuchung Cheng <ycheng@google.com>
>> Signed-off-by: Neal Cardwell <ncardwell@google.com>
>> ---
>
> Acked-by: Eric Dumazet <edumazet@google.com>
Which TCP/IP stacks besides Linux have Fast Open at this point and for
how long have they had it? Basically, how prevalent are servers out
there (both Internet and intranet) with support for Fast Open?
http://news.netcraft.com/archives/2013/11/01/november-2013-web-server-survey.html
doesn't go down to the OS level, and
http://www.netcraft.com/internet-data-mining/ssl-survey/ is only from
May and was in the context of SSL sides, but it does provide an
interesting break-down of "OS share" which looks reasonably stable going
back three years and so probably isn't too far off presently.
<insert the same sort of question about those firewalls and intermediate
devices which make our lives so much fun here>
rick jones
next prev parent reply other threads:[~2013-11-01 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 16:19 [PATCH net-next] tcp: enable sockets to use MSG_FASTOPEN by default Yuchung Cheng
2013-10-31 23:19 ` Eric Dumazet
2013-11-01 15:29 ` Rick Jones [this message]
2013-11-01 16:09 ` Yuchung Cheng
2013-11-05 0:58 ` David Miller
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=5273C8D1.5080608@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=sivasankar@cs.ucsd.edu \
--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;
as well as URLs for NNTP newsgroup(s).