From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v6 mptcp-next 0/9] RM_ADDR: remove a list of addrs
Date: Tue, 09 Feb 2021 23:03:41 +0800 [thread overview]
Message-ID: <cover.1612882689.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
v6:
- add "rm_list->nr = 1" in patch 1.
- apply: tag export/20210209T062213 + patchset "move to next addr and
testcases" v3.
v5:
- use struct mptcp_rm_list instead of the ids array.
- simplify mptcp_pm_remove_addrs_and_subflows.
- apply: tag export/20210207T062839 + patchset "move to next addr and
testcases".
v4:
- use MAX_ADDR_ID as the default value in the rm_ids array.
- keep the free_list and pass it to mptcp_nl_remove_addrs_list.
- handle remove anno_addrs and subflows in one function.
v3:
- avoid looping twice in mptcp_write_options
- drop nr in mptcp_get_rm_ids_nr
- use rm_ids[0] in patch 1 and patch 3
- separate pm.rm_ids for incoming and outgoing
- tag: export/20210131T062218
v2:
- use an array of ids instead of a u64 map
- drop "mptcp: update the netlink event for rm_addr" in v1
- tag: export/20210131T062218
This patchset added the removing a list of addresses support for
RM_ADDR. It addressed issue #140.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/140
Geliang Tang (9):
mptcp: add rm_list in mptcp_out_options
mptcp: add rm_list_tx in mptcp_pm_data
mptcp: add rm_list in mptcp_options_received
mptcp: add rm_list_rx in mptcp_pm_data
mptcp: remove multi addresses in PM
mptcp: remove multi subflows in PM
mptcp: remove multi addresses and subflows in PM
mptcp: remove a list of addrs when flushing
selftests: mptcp: add testcases for removing addrs
include/net/mptcp.h | 9 +-
net/mptcp/options.c | 49 +++++--
net/mptcp/pm.c | 29 ++--
net/mptcp/pm_netlink.c | 138 +++++++++++++-----
net/mptcp/protocol.h | 17 ++-
.../testing/selftests/net/mptcp/mptcp_join.sh | 35 +++++
6 files changed, 205 insertions(+), 72 deletions(-)
--
2.29.2
reply other threads:[~2021-02-09 15:03 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.1612882689.git.geliangtang@gmail.com \
--to=mptcp@lists.linux.dev \
/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