From: Geliang Tang <geliangtang@gmail.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@gmail.com>
Subject: [MPTCP][PATCH v2 mptcp-next 00/10] fullmesh path manager support
Date: Wed, 21 Jul 2021 22:31:24 +0800 [thread overview]
Message-ID: <cover.1626877655.git.geliangtang@gmail.com> (raw)
Implement the in-kernel fullmesh path manager like on the mptcp.org
kernel.
v2:
- Implement the fullmesh mode as an extension to the netlink PM, not a
standalone PM as Paolo suggested.
- drop duplicate code.
- add a new per endpoint flag MPTCP_PM_ADDR_FLAG_FULLMESH.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/193
Geliang Tang (10):
mptcp: add a new sysctl fullmesh_enabled
mptcp: register ipv4 addr notifier
mptcp: register ipv6 addr notifier
mptcp: add netdev up event handler
mptcp: invoke mptcp_nl_remove_subflow_and_signal_addr in rcu_work
mptcp: add netdev down event handler
mptcp: add proc file local_addr_list
selftests: mptcp: print the fullmesh flag
selftests: mptcp: add fullmesh testcases
selftests: mptcp: del uncontinuous removing ids
Documentation/networking/mptcp-sysctl.rst | 8 ++
include/uapi/linux/mptcp.h | 1 +
net/mptcp/Kconfig | 10 ++
net/mptcp/Makefile | 1 +
net/mptcp/ctrl.c | 16 +++
net/mptcp/pm.c | 3 +
net/mptcp/pm_fullmesh.c | 94 ++++++++++++++
net/mptcp/pm_netlink.c | 116 +++++++++++++++++-
net/mptcp/protocol.h | 6 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 91 +++++++++++++-
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 7 ++
11 files changed, 342 insertions(+), 11 deletions(-)
create mode 100644 net/mptcp/pm_fullmesh.c
--
2.31.1
next reply other threads:[~2021-07-21 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 14:31 Geliang Tang [this message]
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 01/10] mptcp: add a new sysctl fullmesh_enabled Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 02/10] mptcp: register ipv4 addr notifier Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 03/10] mptcp: register ipv6 " Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 04/10] mptcp: add netdev up event handler Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 05/10] mptcp: invoke mptcp_nl_remove_subflow_and_signal_addr in rcu_work Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 06/10] mptcp: add netdev down event handler Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 07/10] mptcp: add proc file local_addr_list Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 08/10] selftests: mptcp: print the fullmesh flag Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 09/10] selftests: mptcp: add fullmesh testcases Geliang Tang
2021-07-21 14:31 ` [MPTCP][PATCH v2 mptcp-next 10/10] selftests: mptcp: del uncontinuous removing ids Geliang Tang
2021-07-22 13:34 ` Matthieu Baerts
2021-07-22 13:33 ` [MPTCP][PATCH v2 mptcp-next 07/10] mptcp: add proc file local_addr_list Matthieu Baerts
2021-07-22 13:33 ` [MPTCP][PATCH v2 mptcp-next 04/10] mptcp: add netdev up event handler Matthieu Baerts
2021-07-21 17:08 ` [MPTCP][PATCH v2 mptcp-next 02/10] mptcp: register ipv4 addr notifier Paolo Abeni
2021-07-22 13:33 ` Matthieu Baerts
2021-07-22 13:33 ` [MPTCP][PATCH v2 mptcp-next 01/10] mptcp: add a new sysctl fullmesh_enabled Matthieu Baerts
2021-07-22 15:30 ` [MPTCP][PATCH v2 mptcp-next 00/10] fullmesh path manager support Matthieu Baerts
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.1626877655.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--cc=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 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.