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 v4 mptcp-next 0/5] mptcp: create subflow for newly added address and testcases
Date: Wed, 06 Jan 2021 14:30:04 +0800	[thread overview]
Message-ID: <cover.1609914325.git.geliangtang@gmail.com> (raw)

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

v4:
 - add a new patch to use WRITE_ONCE/READ_ONCE for the pernet *_max.
 - drop pm *_max in mptcp_diag.c too.

v3:
 - add a new patch to drop *_max fields in mptcp_pm_data

v2:
 - drop the unused addr parameter in mptcp_nl_add_subflow_or_signal_addr
 - use the pernet *_max values in mptcp_pm_create_subflow_or_signal_addr
instead of the per-msk values.

Address issue 19 "let PM netlink update live sockets on local addresses
list change". The removed addresses part of this issue is done, this
patchset only implemented the added addresses part.

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

Geliang Tang (5):
  mptcp: use WRITE_ONCE/READ_ONCE for the pernet *_max
  mptcp: drop *_max fields in mptcp_pm_data
  mptcp: create subflow or signal addr for newly added address
  selftests: mptcp: use minus values for removing address numbers
  selftests: mptcp: add testcases for newly added addresses

 net/mptcp/mptcp_diag.c                        |   6 +-
 net/mptcp/pm.c                                |   9 +-
 net/mptcp/pm_netlink.c                        | 150 +++++++++++++-----
 net/mptcp/protocol.h                          |   8 +-
 .../testing/selftests/net/mptcp/mptcp_join.sh | 101 ++++++++++--
 5 files changed, 211 insertions(+), 63 deletions(-)

-- 
2.29.2

                 reply	other threads:[~2021-01-06  6:30 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.1609914325.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.