From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/8] BPF path manager, part 2
Date: Fri, 13 Dec 2024 15:35:21 +0800 [thread overview]
Message-ID: <cover.1734074788.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v2:
- split patch 7 of v1 into two.
- patches 1-6 have no code changes, only the commit logs have been
updated.
- more commit log to explain why mptcp_pm_addr_id_bitmap_t needs to
be defined.
- use mptcp_pm_addr_id_bitmap_t in userspace_pm_append_new_local_addr
too.
In order to implement BPF userspace path manager, it is necessary to
unify the interfaces of the path manager. This set updates get_addr()
and dump_addr() interfaces.
Geliang Tang (8):
mptcp: make three pm wrappers static
mptcp: drop skb parameter of get_addr
mptcp: add id parameter for get_addr
mptcp: reuse sending nlmsg code in get_addr
mptcp: change info of get_addr as const
mptcp: add info parameter for dump_addr
mptcp: add mptcp_pm_addr_id_bitmap_t type
mptcp: reuse sending nlmsg code in dump_addr
include/net/mptcp.h | 7 +++
net/mptcp/pm.c | 108 ++++++++++++++++++++++++++++++++++++---
net/mptcp/pm_netlink.c | 105 ++++++-------------------------------
net/mptcp/pm_userspace.c | 102 ++++++++++--------------------------
net/mptcp/protocol.h | 21 +++-----
5 files changed, 157 insertions(+), 186 deletions(-)
--
2.45.2
next reply other threads:[~2024-12-13 7:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 7:35 Geliang Tang [this message]
2024-12-13 7:35 ` [PATCH mptcp-next v2 1/8] mptcp: make three pm wrappers static Geliang Tang
2024-12-13 7:35 ` [PATCH mptcp-next v2 2/8] mptcp: drop skb parameter of get_addr Geliang Tang
2024-12-13 7:35 ` [PATCH mptcp-next v2 3/8] mptcp: add id parameter for get_addr Geliang Tang
2024-12-30 16:29 ` Matthieu Baerts
2024-12-13 7:35 ` [PATCH mptcp-next v2 4/8] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2024-12-13 7:35 ` [PATCH mptcp-next v2 5/8] mptcp: change info of get_addr as const Geliang Tang
2024-12-30 16:29 ` Matthieu Baerts
2024-12-13 7:35 ` [PATCH mptcp-next v2 6/8] mptcp: add info parameter for dump_addr Geliang Tang
2024-12-13 7:35 ` [PATCH mptcp-next v2 7/8] mptcp: add mptcp_pm_addr_id_bitmap_t type Geliang Tang
2024-12-30 16:30 ` Matthieu Baerts
2025-01-09 4:15 ` Geliang Tang
2025-01-09 15:37 ` Matthieu Baerts
2024-12-13 7:35 ` [PATCH mptcp-next v2 8/8] mptcp: reuse sending nlmsg code in dump_addr Geliang Tang
2024-12-30 16:33 ` Matthieu Baerts
2024-12-30 16:27 ` [PATCH mptcp-next v2 0/8] BPF path manager, part 2 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.1734074788.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