From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v4 0/2] mptcp: improve ADD_ADDR timeout handling
Date: Tue, 12 Aug 2025 16:39:14 +0800 [thread overview]
Message-ID: <cover.1754987655.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v4:
- rollback to v2, just use icsk->icsk_rto.
Depends on:
- mptcp: disable add_addr retrans, v2
Based-on: <cover.1754534416.git.tanggeliang@kylinos.cn>
v3:
- a new patch, remove duplicate sk_reset_timer call
- use __tcp_set_rto() * 2 instead of icsk->icsk_rto
- update selftests.
- https://patchwork.kernel.org/project/mptcp/cover/cover.1754449947.git.tanggeliang@kylinos.cn/
v2:
- do not rename add_addr_timeout
- use icsk->icsk_rto instead of tp->srtt_us
- increase the time after each retransmission
- https://patchwork.kernel.org/project/mptcp/patch/40706ad511220729207ccd7cf48e320e4d0d7dea.1754028199.git.tanggeliang@kylinos.cn/
v1:
- https://patchwork.kernel.org/project/mptcp/cover/cover.1753777199.git.tanggeliang@kylinos.cn/
Geliang Tang (2):
mptcp: make ADD_ADDR retransmission timeout adaptive
selftests: mptcp: remove add_addr_timeout settings
Documentation/networking/mptcp-sysctl.rst | 4 +--
net/mptcp/pm.c | 28 ++++++++++++++++---
.../testing/selftests/net/mptcp/mptcp_join.sh | 3 --
3 files changed, 26 insertions(+), 9 deletions(-)
--
2.48.1
next reply other threads:[~2025-08-12 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:39 Geliang Tang [this message]
2025-08-12 8:39 ` [PATCH mptcp-next v4 1/2] mptcp: make ADD_ADDR retransmission timeout adaptive Geliang Tang
2025-08-15 15:29 ` Matthieu Baerts
2025-08-12 8:39 ` [PATCH mptcp-next v4 2/2] selftests: mptcp: remove add_addr_timeout settings Geliang Tang
2025-09-02 16:52 ` Matthieu Baerts
2025-08-12 10:27 ` [PATCH mptcp-next v4 0/2] mptcp: improve ADD_ADDR timeout handling MPTCP CI
2025-08-15 15:24 ` Matthieu Baerts
2025-08-18 10:52 ` Matthieu Baerts
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.1754987655.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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;
as well as URLs for NNTP newsgroup(s).