From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/6] add refcount for address entry
Date: Thu, 2 Nov 2023 18:05:51 +0800 [thread overview]
Message-ID: <cover.1698919435.git.geliang.tang@suse.com> (raw)
v2:
- rebased with "add flush and dump for userspace pm" series.
Add refcount for address entry.
Geliang Tang (6):
selftests: mptcp: add mptcp_lib_evts_*
selftests: mptcp: userspace: print colored results
mptcp: dup an entry when removing it
mptcp: add userspace pm addr entry refcount
selftests: mptcp: rm userspace addr with randowly order
mptcp: add netlink pm addr entry refcount
net/mptcp/pm_netlink.c | 19 +++--
net/mptcp/pm_userspace.c | 39 +++++++---
net/mptcp/protocol.h | 2 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 72 +++++++++----------
.../testing/selftests/net/mptcp/mptcp_lib.sh | 63 ++++++++++++++++
.../selftests/net/mptcp/userspace_pm.sh | 42 +++--------
6 files changed, 150 insertions(+), 87 deletions(-)
--
2.35.3
next reply other threads:[~2023-11-02 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 10:05 Geliang Tang [this message]
2023-11-02 10:05 ` [PATCH mptcp-next v2 1/6] selftests: mptcp: add mptcp_lib_evts_* Geliang Tang
2023-11-02 10:05 ` [PATCH mptcp-next v2 2/6] selftests: mptcp: userspace: print colored results Geliang Tang
2023-11-02 10:05 ` [PATCH mptcp-next v2 3/6] mptcp: dup an entry when removing it Geliang Tang
2023-11-02 10:05 ` [PATCH mptcp-next v2 4/6] mptcp: add userspace pm addr entry refcount Geliang Tang
2023-11-02 10:05 ` [PATCH mptcp-next v2 5/6] selftests: mptcp: rm userspace addr with randowly order Geliang Tang
2023-11-02 10:05 ` [PATCH mptcp-next v2 6/6] mptcp: add netlink pm addr entry refcount Geliang Tang
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.1698919435.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--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.