From: Geliang Tang <geliang.tang@linux.dev>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@linux.dev>
Subject: [PATCH mptcp-next v2 00/15] dump for userspace pm
Date: Mon, 18 Dec 2023 17:23:29 +0800 [thread overview]
Message-ID: <cover.1702891194.git.geliang.tang@linux.dev> (raw)
v2:
Address Mat's comments in v1:
- patch 2: pass token to dump_addr too.
- patch 2: add back id in mptcp_userspace_pm_dump_addr().
- patch 5: pdate mptcp.yaml
v1:
Address Mat's comments in "userspace pm enhancements" v14.
Geliang Tang (15):
mptcp: add mptcp_pm_nl_put_entry_msg helper
mptcp: implement mptcp_userspace_pm_dump_addr
mptcp: dump addrs in userspace pm list
mptcp: check userspace pm subflow flag
mptcp: add token for get-addr in yaml
selftests: mptcp: add userspace pm subflow flag
selftests: mptcp: add token for dump_addr
selftests: mptcp: add check_output helper
selftests: mptcp: dump userspace addrs list
mptcp: add userspace_pm_lookup_addr_by_id helper
mptcp: add mptcp_pm_nl_put_entry_info helper
mptcp: implement mptcp_userspace_pm_get_addr
mptcp: get addr in userspace pm list
selftests: mptcp: add token for get_addr
selftests: mptcp: userspace pm get addr tests
Documentation/netlink/specs/mptcp.yaml | 5 +-
net/mptcp/mptcp_pm_gen.c | 7 +-
net/mptcp/mptcp_pm_gen.h | 2 +-
net/mptcp/pm_netlink.c | 95 +++++++++++-----
net/mptcp/pm_userspace.c | 103 +++++++++++++++---
net/mptcp/protocol.h | 9 ++
.../testing/selftests/net/mptcp/mptcp_join.sh | 99 +++++++++++++++++
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 39 ++++++-
8 files changed, 306 insertions(+), 53 deletions(-)
--
2.35.3
next reply other threads:[~2023-12-18 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:23 Geliang Tang [this message]
2023-12-18 9:23 ` [PATCH mptcp-next v2 01/15] mptcp: add mptcp_pm_nl_put_entry_msg helper Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 02/15] mptcp: implement mptcp_userspace_pm_dump_addr Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 03/15] mptcp: dump addrs in userspace pm list Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 04/15] mptcp: check userspace pm subflow flag Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 05/15] mptcp: add token for get-addr in yaml Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 06/15] selftests: mptcp: add userspace pm subflow flag Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 07/15] selftests: mptcp: add token for dump_addr Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 08/15] selftests: mptcp: add check_output helper Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 09/15] selftests: mptcp: dump userspace addrs list Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 10/15] mptcp: add userspace_pm_lookup_addr_by_id helper Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 11/15] mptcp: add mptcp_pm_nl_put_entry_info helper Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 12/15] mptcp: implement mptcp_userspace_pm_get_addr Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 13/15] mptcp: get addr in userspace pm list Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 14/15] selftests: mptcp: add token for get_addr Geliang Tang
2023-12-18 9:23 ` [PATCH mptcp-next v2 15/15] selftests: mptcp: userspace pm get addr tests Geliang Tang
2023-12-18 10:58 ` selftests: mptcp: userspace pm get addr tests: Tests Results 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.1702891194.git.geliang.tang@linux.dev \
--to=geliang.tang@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox