From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v4 0/7] BPF path manager, part 2
Date: Fri, 10 Jan 2025 15:36:13 +0800 [thread overview]
Message-ID: <cover.1736494320.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v4:
- move "mptcp: userspace pm set_flags id support" out of this set.
- only add 'local' parameter for set_flags, no 'remote'.
Based-on: <cover.1736493803.git.tanggeliang@kylinos.cn>
v3:
- Thanks Matt for the review on dump_addr interfaces. It seems that
it needs more time to be modified. In this version, I removed the
patches for dump_addr interfaces from this set and added the patches
for set_flags interfaces.
- set_flags interfaces patches address Matt's comments on the set
"mptcp: use GENL_REQ_ATTR_CHECK in userspace pm" v2.
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 (7):
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: drop skb parameter of set_flags
mptcp: change rem type of set_flags
mptcp: add local parameter for set_flags
net/mptcp/pm.c | 86 +++++++++++++++++++++++++++++---
net/mptcp/pm_netlink.c | 104 ++++++++-------------------------------
net/mptcp/pm_userspace.c | 81 +++++++-----------------------
net/mptcp/protocol.h | 14 +++---
4 files changed, 124 insertions(+), 161 deletions(-)
--
2.45.2
next reply other threads:[~2025-01-10 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 7:36 Geliang Tang [this message]
2025-01-10 7:36 ` [PATCH mptcp-next v4 1/7] mptcp: make three pm wrappers static Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 2/7] mptcp: drop skb parameter of get_addr Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 3/7] mptcp: add id parameter for get_addr Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 4/7] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 5/7] mptcp: drop skb parameter of set_flags Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 6/7] mptcp: change rem type " Geliang Tang
2025-01-10 7:36 ` [PATCH mptcp-next v4 7/7] mptcp: add local parameter for set_flags Geliang Tang
2025-01-10 11:53 ` Matthieu Baerts
2025-01-10 9:12 ` [PATCH mptcp-next v4 0/7] BPF path manager, part 2 MPTCP CI
2025-01-10 11:53 ` Matthieu Baerts
2025-01-10 12:40 ` Geliang Tang
2025-01-12 13:09 ` 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.1736494320.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