All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Krystad <peter.krystad at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH v2 0/6] IPv6 support
Date: Tue, 05 Nov 2019 20:41:27 -0800	[thread overview]
Message-ID: <20191106044133.14418-1-peter.krystad@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

Implemented support for IPv6. selftests pass with ipv6=true, but
they take twice as long to run...

With re-factoring the addition of IPv6 is very clean but I did not
split files yet as it will be hard to squash any changes after the
such a split.

Still to do: multiple subflows, handling IPv4-mapped connections.

v2: Added further re-factoring that makes IPv6 change even smaller
    Add mptcpv6_init() stub and verified build with IPv6=n and m

    Kconfig changes submitted in earlier patch set, this set depends
    on those changes being merged.

    Squashing the final patch (6/6) so that IPv6 support occurs before
    the kselftests commit will be complicated.

Peter Krystad (6):
  mptcp: Reference icsk_af_ops routines through saved pointer
  mptcp: Reference inet_stream_ops routines through socket->ops
  mptcp: Re-factor mptcp_getname routine to be af-agnostic
  mptcp: Re-factor subflow_v4_conn_request to be af-agnostic
  mptcp: Export low-level routines for IPv6
  mptcp: Add IPv6 support

 include/net/mptcp.h  |  10 ++++
 include/net/tcp.h    |   3 ++
 net/ipv6/tcp_ipv6.c  |  16 ++++--
 net/mptcp/ctrl.c     |  11 ++++
 net/mptcp/protocol.c | 117 ++++++++++++++++++++++++++++++++-----------
 net/mptcp/protocol.h |   7 +++
 net/mptcp/subflow.c  |  94 +++++++++++++++++++++++++++++-----
 7 files changed, 213 insertions(+), 45 deletions(-)

-- 
2.17.2

                 reply	other threads:[~2019-11-06  4:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191106044133.14418-1-peter.krystad@linux.intel.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.