From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v2 mptcp-next 0/7] RM_ADDR: remove a list of addrs
Date: Mon, 01 Feb 2021 15:11:09 +0800 [thread overview]
Message-ID: <cover.1612163150.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
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 (7):
mptcp: remove multi addrs on outgoing path
mptcp: remove multi addrs on incoming path
mptcp: remove multi addresses in PM
mptcp: remove multi subflows in PM
mptcp: implement mptcp_nl_remove_addrs_and_subflows
mptcp: remove a list of addrs when flushing
selftests: mptcp: add testcases for removing addrs
include/net/mptcp.h | 4 +-
net/mptcp/options.c | 55 +++--
net/mptcp/pm.c | 28 +--
net/mptcp/pm_netlink.c | 190 ++++++++++++++----
net/mptcp/protocol.h | 26 ++-
.../testing/selftests/net/mptcp/mptcp_join.sh | 23 +++
6 files changed, 252 insertions(+), 74 deletions(-)
--
2.29.2
reply other threads:[~2021-02-01 7:11 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.1612163150.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