From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v2 mptcp-next 0/7] mptcp: autotune related improvement
Date: Tue, 4 Nov 2025 22:51:34 +0100 [thread overview]
Message-ID: <cover.1762292476.git.pabeni@redhat.com> (raw)
This series collects a few follow-up for the backlog refactor, with some
of them posing as fixes just to confuse the enemy (or feel the season
mood)
Targeting net-next as the issues addressed are very old, the change
is quite invasive and, as mentioned, based on the BL refactor.
Only patch 2/7 could be considered for net, but still included because
somewhat related to the others and to keep my life easy.
Overall this:
- introduces a tracepoint similar to tcp useful to track down the issues
addressed here
- avoid rx drop in corner case scenarios, improving tput stability and
peak tput over fast link
- refactor the rcv space and rtt estimator, overall making DRS more
correct and avoiding rcv buffer drifting to tcp_rmem[2], which in
turn makes the tput more stable and less bursty
---
v1 -> v2:
- new patch 1/7
- old patch 2/4 has been split in 3: 3/7, 4/7 and 5/7
- refactor both the rcv space init and rtt estimator
Paolo Abeni (7):
trace: mptcp: add mptcp_rcvbuf_grow tracepoint
mptcp: avoid unneeded subflow-level drops.
mptcp: fix receive space timestamp initialization.
mptcp: consolidate rcv space init
mptcp: better rcv space initialization
mptcp: better mptcp-level rtt estimator
mptcp: add receive queue awareness in tcp_rcv_space_adjust()
include/trace/events/mptcp.h | 74 +++++++++++++++++
net/mptcp/options.c | 31 +++++++
net/mptcp/protocol.c | 154 ++++++++++++++++++++++-------------
net/mptcp/protocol.h | 44 +++++++++-
net/mptcp/subflow.c | 5 +-
5 files changed, 247 insertions(+), 61 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-04 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 21:51 Paolo Abeni [this message]
2025-11-04 21:51 ` [PATCH v2 mptcp-next 1/7] trace: mptcp: add mptcp_rcvbuf_grow tracepoint Paolo Abeni
2025-11-05 0:24 ` Mat Martineau
2025-11-05 9:40 ` Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 2/7] mptcp: avoid unneeded subflow-level drops Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 3/7] mptcp: fix receive space timestamp initialization Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 4/7] mptcp: consolidate rcv space init Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 5/7] mptcp: better rcv space initialization Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 6/7] mptcp: better mptcp-level rtt estimator Paolo Abeni
2025-11-04 21:51 ` [PATCH v2 mptcp-next 7/7] mptcp: add receive queue awareness in tcp_rcv_space_adjust() Paolo Abeni
2025-11-05 11:27 ` [PATCH v2 mptcp-next 0/7] mptcp: autotune related improvement 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.1762292476.git.pabeni@redhat.com \
--to=pabeni@redhat.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.