All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v5 mptcp-next 0/3] add ADD_ADDR IPv6 support
Date: Wed, 21 Oct 2020 15:19:50 +0800	[thread overview]
Message-ID: <cover.1603264085.git.geliangtang@gmail.com> (raw)

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

v5:
 - drop msleep() in v4
 - drop MPTCP_ADD_ADDR_SEND_ACK in v4
 - add WRITE_ONCE/READ_ONCE for msk->pm.add_addr_signal
 - depend on "mptcp: keep unaccepted MPC subflow into join list"

v4:
 - update the patches as Paolo suggested:
 - change the 'add_addr_signal' type
 - set MPTCP_ADD_ADDR_IPV6 in mptcp_pm_announce_addr
 - add a new helper mptcp_send_dedicated_add_addr_packet to sent out a
new pure ACK packet
 - drop other MPTCP suboptions in mptcp_established_options_add_addr

v3:
 - drop other MPTCP suboptions instead of OPTION_TS

v2:
 - avoid adding new field to tcp_sock, add new field in mptcp_pm_data.
 - drop OPTION_TS in mptcp_established_options_add_addr, not in
tcp_established_options.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/55

Geliang Tang (3):
  mptcp: change add_addr_signal type
  mptcp: send out dedicated ADD_ADDR packet
  selftests: mptcp: add ADD_ADDR IPv6 test cases

 net/mptcp/options.c                           | 25 ++++++-
 net/mptcp/pm.c                                | 23 +++---
 net/mptcp/pm_netlink.c                        | 27 +++++++
 net/mptcp/protocol.c                          |  2 +-
 net/mptcp/protocol.h                          | 13 +++-
 .../testing/selftests/net/mptcp/mptcp_join.sh | 70 ++++++++++++++++++-
 6 files changed, 144 insertions(+), 16 deletions(-)

-- 
2.26.2

                 reply	other threads:[~2020-10-21  7:19 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=cover.1603264085.git.geliangtang@gmail.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.