From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v3 00/15] refactor PM interfaces
Date: Thu, 10 Oct 2024 13:47:45 +0800 [thread overview]
Message-ID: <cover.1728538975.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v3:
- two more patches, 14-15, drop struct mptcp_pm_local and struct
mptcp_pm_add_entry.
v2:
- split patch 5 into two.
- new patches 9-13.
In order to implement BPF path manager, this set refactors get_addr
and dump_addr interfaces of PM.
Depends on:
- cleanups for PM interfaces, v3
Based-on: <cover.1728298100.git.tanggeliang@kylinos.cn>
Geliang Tang (15):
mptcp: add id parameter for get_addr
mptcp: add addr parameter for get_addr
mptcp: reuse sending nlmsg code in get_addr
mptcp: change info of get_addr as const
mptcp: refactor dump_addr with id bitmap
mptcp: refactor dump_addr with get_addr
mptcp: reuse sending nlmsg code in dump_addr
mptcp: add loc and rem for set_flags
mptcp: update address type of get_local_id
mptcp: change is_backup interfaces as get_flags
mptcp: hold pm lock when deleting entry
mptcp: rename mptcp_pm_remove_addrs
mptcp: drop free_list for deleting entries
mptcp: drop struct mptcp_pm_local
mptcp: drop struct mptcp_pm_add_entry
net/mptcp/pm.c | 17 ++-
net/mptcp/pm_netlink.c | 245 ++++++++++++++++++++-------------------
net/mptcp/pm_userspace.c | 168 ++++++++-------------------
net/mptcp/protocol.h | 50 ++++----
net/mptcp/subflow.c | 2 +-
5 files changed, 220 insertions(+), 262 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-10 5:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 5:47 Geliang Tang [this message]
2024-10-10 5:47 ` [PATCH mptcp-next v3 01/15] mptcp: add id parameter for get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 02/15] mptcp: add addr " Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 03/15] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 04/15] mptcp: change info of get_addr as const Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 05/15] mptcp: refactor dump_addr with id bitmap Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 06/15] mptcp: refactor dump_addr with get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 07/15] mptcp: reuse sending nlmsg code in dump_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 08/15] mptcp: add loc and rem for set_flags Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 09/15] mptcp: update address type of get_local_id Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 10/15] mptcp: change is_backup interfaces as get_flags Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 11/15] mptcp: hold pm lock when deleting entry Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 12/15] mptcp: rename mptcp_pm_remove_addrs Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 13/15] mptcp: drop free_list for deleting entries Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 14/15] mptcp: drop struct mptcp_pm_local Geliang Tang
2024-10-10 5:48 ` [PATCH mptcp-next v3 15/15] mptcp: drop struct mptcp_pm_add_entry Geliang Tang
2024-10-10 6:52 ` [PATCH mptcp-next v3 00/15] refactor PM interfaces MPTCP CI
2024-10-10 8:22 ` 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.1728538975.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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