tcp: enable sockets to use MSG_FASTOPEN by default

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>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 2 insertions, 2 deletions

diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index a46d78583ae1..6c0098359ca6 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -451,7 +451,7 @@ tcp_fastopen - INTEGER
         connect() to perform a TCP handshake automatically.
 
         The values (bitmap) are
-        1: Enables sending data in the opening SYN on the client.
+        1: Enables sending data in the opening SYN on the client w/ MSG_FASTOPEN.
         2: Enables TCP Fast Open on the server side, i.e., allowing data in
            a SYN packet to be accepted and passed to the application before
            3-way hand shake finishes.
@@ -464,7 +464,7 @@ tcp_fastopen - INTEGER
            different ways of setting max_qlen without the TCP_FASTOPEN socket
            option.
 
-        Default: 0
+        Default: 1
 
         Note that the client & server side Fast Open flags (1 and 2
         respectively) must be also enabled before the rest of flags can take