From: menglong8.dong@gmail.com
To: mathew.j.martineau@linux.intel.com
Cc: mptcp@lists.linux.dev, Menglong Dong <imagedong@tencent.com>
Subject: [PATCH mptcp-next v3 0/3] mptcp: add statistics for mptcp socket in use
Date: Fri, 30 Sep 2022 10:46:04 +0800 [thread overview]
Message-ID: <20220930024607.128202-1-imagedong@tencent.com> (raw)
From: Menglong Dong <imagedong@tencent.com>
In the 1th patch, we do some code cleanup with replease 'sock->sk'
with 'sk'. In the 2th patch, we add statistics for mptcp socket in
use. And in the 3th patch, we add the testing for this commit.
Changes since v2:
- add testing
Changes since v1:
- split the code cleanup into the 1th patch.
- decrease the statistics for listening mptcp socket inuse with
mptcp_listen_inuse_dec()
- add MPTCP_DESTROIED flags to store if mptcp_destroy_common() was
called on the msk. For fallback case, we need to decrease the
statistics only once, and mptcp_destroy_common() can be called
more than once.
Menglong Dong (3):
mptcp: introduce 'sk' to replace 'sock->sk' in mptcp_listen()
mptcp: add statistics for mptcp socket in use
selftest: mptcp: add test for mptcp socket in use
net/mptcp/protocol.c | 35 ++++++++++++++++++-----
net/mptcp/protocol.h | 1 +
net/mptcp/subflow.c | 3 ++
tools/testing/selftests/net/mptcp/diag.sh | 28 ++++++++++++++++++
4 files changed, 60 insertions(+), 7 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-30 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 2:46 menglong8.dong [this message]
2022-09-30 2:46 ` [PATCH mptcp-next v3 1/3] mptcp: introduce 'sk' to replace 'sock->sk' in mptcp_listen() menglong8.dong
2022-09-30 2:46 ` [PATCH mptcp-next v3 2/3] mptcp: add statistics for mptcp socket in use menglong8.dong
2022-09-30 23:25 ` Mat Martineau
2022-10-06 5:20 ` Menglong Dong
2022-09-30 2:46 ` [PATCH mptcp-next v3 3/3] selftest: mptcp: add test " menglong8.dong
2022-10-06 17:25 ` selftest: mptcp: add test for mptcp socket in use: 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=20220930024607.128202-1-imagedong@tencent.com \
--to=menglong8.dong@gmail.com \
--cc=imagedong@tencent.com \
--cc=mathew.j.martineau@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox