From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Cc: martineau@kernel.org
Subject: [PATCH v7 mptcp-next 0/6] mptcp: autotune related improvement
Date: Thu, 20 Nov 2025 09:39:44 +0100 [thread overview]
Message-ID: <cover.1763625391.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.
Targeting net-next as the issues addressed are very old, the change
is quite invasive and, as mentioned, based on the BL refactor.
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
Note that after this upstream series will be merged:
https://patchwork.kernel.org/user/todo/netdevbpf/?series=1025209
we want to introduce similar changes in mptcp, too.
I'm sorry for the high frequency spamming; trying to complete this
stuff before ENORESOURCES. Please ignore the previous 2 revisions.
---
v6 -> v7:
- re added the patches dropped in the last 2 iterations
v5 -> v6:
- dropped the buggy patch 3/5
v4 -> v5:
- dropped patch 4/6; it proved to be useless together with new version
of patch 4/5
- refactor rtt estimator: use sliding window instead of dropping "too
high" values
v3 -> v4:
- dropped already merged patch 1
- update comment in patch 6/6
v2 -> v3:
- use __entry->family in patch 1/7
- more verbose commit message for patch 6/7
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 (6):
trace: mptcp: add mptcp_rcvbuf_grow tracepoint
mptcp: do not account for OoO in mptcp_rcvbuf_grow()
mptcp: fix receive space timestamp initialization.
mptcp: consolidate rcv space init
mptcp: better mptcp-level RTT estimator
mptcp: add receive queue awareness in tcp_rcv_space_adjust()
include/trace/events/mptcp.h | 80 ++++++++++++++++++++++++
net/mptcp/protocol.c | 116 ++++++++++++++++++-----------------
net/mptcp/protocol.h | 44 ++++++++++++-
net/mptcp/subflow.c | 2 -
4 files changed, 183 insertions(+), 59 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-20 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 8:39 Paolo Abeni [this message]
2025-11-20 8:39 ` [PATCH v7 mptcp-next 1/6] trace: mptcp: add mptcp_rcvbuf_grow tracepoint Paolo Abeni
2025-11-20 8:39 ` [PATCH v7 mptcp-next 2/6] mptcp: do not account for OoO in mptcp_rcvbuf_grow() Paolo Abeni
2025-11-27 0:06 ` Mat Martineau
2025-11-20 8:39 ` [PATCH v7 mptcp-next 3/6] mptcp: fix receive space timestamp initialization Paolo Abeni
2025-11-20 8:39 ` [PATCH v7 mptcp-next 4/6] mptcp: consolidate rcv space init Paolo Abeni
2025-11-20 8:39 ` [PATCH v7 mptcp-next 5/6] mptcp: better mptcp-level RTT estimator Paolo Abeni
2025-11-27 2:19 ` Mat Martineau
2025-11-27 7:36 ` Paolo Abeni
2025-11-27 18:13 ` Matthieu Baerts
2025-11-28 8:47 ` Paolo Abeni
2025-11-28 9:51 ` Matthieu Baerts
2025-12-16 16:38 ` Matthieu Baerts
2025-11-20 8:39 ` [PATCH v7 mptcp-next 6/6] mptcp: add receive queue awareness in tcp_rcv_space_adjust() Paolo Abeni
2025-11-20 9:48 ` [PATCH v7 mptcp-next 0/6] mptcp: autotune related improvement MPTCP CI
2025-11-27 18:42 ` 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.1763625391.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=martineau@kernel.org \
--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.