netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuchung Cheng <ycheng@google.com>
To: davem@davemloft.net, ncardwell@google.com, edumazet@google.com
Cc: longinus00@gmail.com, hkchu@google.com, netdev@vger.kernel.org,
	Yuchung Cheng <ycheng@google.com>
Subject: [PATCH 0/5] tcp: IPv6 support for fastopen server
Date: Sun, 11 May 2014 20:22:08 -0700	[thread overview]
Message-ID: <1399864933-28287-1-git-send-email-ycheng@google.com> (raw)

This patch series add IPv6 support for fastopen server. To minimize
code duplication in IPv4 and IPv6, the current v4 only code is
refactored and common code is moved into net/ipv4/tcp_fastopen.c.

Also the current code uses a different function from
tcp_v4_send_synack() to send the first SYN-ACK in fastopen.
The new code eliminates this separate function by refactoring the
child-socket and syn-ack creation code.  After these refactoring
in the first four patches, we can easily add the fastopen code in
IPv6 by changing corresponding IPv6 functions.

Note Fast Open client already supports IPv6. This patch is for
the server-side (passive open) IPv6 support only.

Daniel Lee (1):
  tcp: IPv6 support for fastopen server

Yuchung Cheng (4):
  tcp: move fastopen functions to tcp_fastopen.c
  tcp: simplify fast open cookie processing
  tcp: use tcp_v4_send_synack on first SYN-ACK
  tcp: improve fastopen icmp handling

 include/linux/tcp.h      |   5 -
 include/net/tcp.h        |  15 ++-
 net/ipv4/tcp_fastopen.c  | 219 +++++++++++++++++++++++++++++++++++--
 net/ipv4/tcp_ipv4.c      | 277 +++++------------------------------------------
 net/ipv4/tcp_minisocks.c |  31 ++++++
 net/ipv4/tcp_output.c    |  23 +---
 net/ipv6/tcp_ipv6.c      |  62 ++++++++---
 7 files changed, 323 insertions(+), 309 deletions(-)

-- 
1.9.1.423.g4596e3a

             reply	other threads:[~2014-05-12  3:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  3:22 Yuchung Cheng [this message]
2014-05-12  3:22 ` [PATCH 1/5] tcp: move fastopen functions to tcp_fastopen.c Yuchung Cheng
2014-05-12 19:16   ` Neal Cardwell
2014-05-12  3:22 ` [PATCH 2/5] tcp: simplify fast open cookie processing Yuchung Cheng
2014-05-12 19:23   ` Neal Cardwell
2014-05-12  3:22 ` [PATCH 3/5] tcp: use tcp_v4_send_synack on first SYN-ACK Yuchung Cheng
2014-05-12 19:29   ` Neal Cardwell
2014-05-12  3:22 ` [PATCH 4/5] tcp: improve fastopen icmp handling Yuchung Cheng
2014-05-12 19:30   ` Neal Cardwell
2014-05-12  3:22 ` [PATCH 5/5] tcp: IPv6 support for fastopen server Yuchung Cheng
2014-05-12 19:35   ` Neal Cardwell
2014-05-12  3:26 ` [PATCH 0/5] " Yuchung Cheng
2014-05-12  3:33   ` David Miller
2014-05-13 21:54 ` 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=1399864933-28287-1-git-send-email-ycheng@google.com \
    --to=ycheng@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkchu@google.com \
    --cc=longinus00@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    /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).