From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang@kernel.org>
Subject: [PATCH mptcp-next 0/7] BPF path manager, part 2
Date: Sat, 7 Dec 2024 09:07:20 +0800 [thread overview]
Message-ID: <cover.1733533215.git.geliang@kernel.org> (raw)
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: change info of get_addr as const
mptcp: add info parameter for dump_addr
mptcp: reuse sending nlmsg code in dump_addr
include/net/mptcp.h | 7 +++
net/mptcp/pm.c | 107 ++++++++++++++++++++++++++++++++++++---
net/mptcp/pm_netlink.c | 105 ++++++--------------------------------
net/mptcp/pm_userspace.c | 94 ++++++++--------------------------
net/mptcp/protocol.h | 21 +++-----
5 files changed, 152 insertions(+), 182 deletions(-)
--
2.45.2
next reply other threads:[~2024-12-07 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 1:07 Geliang Tang [this message]
2024-12-07 1:07 ` [PATCH mptcp-next 1/7] mptcp: make three pm wrappers static Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 2/7] mptcp: drop skb parameter of get_addr Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 3/7] mptcp: add id parameter for get_addr Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 4/7] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 5/7] mptcp: change info of get_addr as const Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 6/7] mptcp: add info parameter for dump_addr Geliang Tang
2024-12-07 1:07 ` [PATCH mptcp-next 7/7] mptcp: reuse sending nlmsg code in dump_addr Geliang Tang
2024-12-07 2:10 ` [PATCH mptcp-next 0/7] BPF path manager, part 2 MPTCP CI
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.1733533215.git.geliang@kernel.org \
--to=geliang@kernel.org \
--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.