From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v4 0/2] mptcp: refactor MP_FAIL response
Date: Thu, 9 Jun 2022 08:00:51 +0800 [thread overview]
Message-ID: <cover.1654732564.git.geliang.tang@suse.com> (raw)
v4:
- rename fail_sock to fail_ssk, fail_timeout to fail_tout.
- move fail_ssk and fail_tout check from mptcp_mp_fail_no_response to
mptcp_worker
- split into two patches.
Geliang Tang (2):
mptcp: refactor MP_FAIL response timeout
mptcp: trace MP_FAIL subflow in mptcp_sock
net/mptcp/pm.c | 7 ++-----
net/mptcp/protocol.c | 37 +++++++++++--------------------------
net/mptcp/protocol.h | 3 ++-
net/mptcp/subflow.c | 12 +++---------
4 files changed, 18 insertions(+), 41 deletions(-)
--
2.35.3
next reply other threads:[~2022-06-09 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 0:00 Geliang Tang [this message]
2022-06-09 0:00 ` [PATCH mptcp-next v4 1/2] mptcp: refactor MP_FAIL response timeout Geliang Tang
2022-06-09 15:03 ` Paolo Abeni
2022-06-09 17:29 ` Mat Martineau
2022-06-09 0:00 ` [PATCH mptcp-next v4 2/2] mptcp: trace MP_FAIL subflow in mptcp_sock Geliang Tang
2022-06-09 0:31 ` Mat Martineau
2022-06-09 1:23 ` Geliang Tang
2022-06-09 15:01 ` Matthieu Baerts
2022-06-09 1:25 ` mptcp: trace MP_FAIL subflow in mptcp_sock: 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.1654732564.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.