From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [RFC mptcp-next v2 0/6] MP_FAIL echo and retrans
Date: Thu, 17 Feb 2022 19:23:38 +0800 [thread overview]
Message-ID: <cover.1645096378.git.geliang.tang@suse.com> (raw)
v2:
- Only send MP_FAIL response in the single subflow case
- Reuse icsk_retransmit_timer to trigger the retransmission.
- Patch 6 still doesn't work, needs Matt's help.
Geliang Tang (6):
mptcp: add MP_FAIL echo support
mptcp: add mibs for MP_FAIL echo
selftests: mptcp: add MP_FAIL echo mibs check
mptcp: add a new sysctl mp_fail_timeout
mptcp: add MP_FAIL retrans support
selftests: mptcp: MP_FAIL timeout testcases TODO
Documentation/networking/mptcp-sysctl.rst | 10 +++
net/mptcp/ctrl.c | 14 ++++
net/mptcp/mib.c | 2 +
net/mptcp/mib.h | 2 +
net/mptcp/pm.c | 13 +++-
net/mptcp/protocol.c | 44 +++++++++++-
net/mptcp/protocol.h | 4 ++
net/mptcp/subflow.c | 3 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 72 +++++++++++++++++++
9 files changed, 161 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-17 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 11:23 Geliang Tang [this message]
2022-02-17 11:23 ` [RFC mptcp-next v2 1/6] mptcp: add MP_FAIL echo support Geliang Tang
2022-02-24 1:42 ` Mat Martineau
2022-02-17 11:23 ` [RFC mptcp-next v2 2/6] mptcp: add mibs for MP_FAIL echo Geliang Tang
2022-02-17 11:23 ` [RFC mptcp-next v2 3/6] selftests: mptcp: add MP_FAIL echo mibs check Geliang Tang
2022-02-17 11:23 ` [RFC mptcp-next v2 4/6] mptcp: add a new sysctl mp_fail_timeout Geliang Tang
2022-02-24 1:44 ` Mat Martineau
2022-02-17 11:23 ` [RFC mptcp-next v2 5/6] mptcp: add MP_FAIL retrans support Geliang Tang
2022-02-24 1:54 ` Mat Martineau
2022-02-17 11:23 ` [RFC mptcp-next v2 6/6] selftests: mptcp: MP_FAIL timeout testcases TODO 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.1645096378.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.