All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v9 mptcp-next 0/6] mptcp: address stall under memory pressure
Date: Wed, 27 May 2026 12:45:30 +0200	[thread overview]
Message-ID: <cover.1779876523.git.pabeni@redhat.com> (raw)

This an attempt to fix the data transfer stall reported by Geliang and
Gang more carefully enforcing memory constraints at the MPTCP level.

This iteration introduces has no significant change over the previous
one; the already merged patches has been dropped, and the remaining ones
rebases on top. The main delta is the commit message for patch 4, here
completely reworderd, as its content become obsoleted in the past
reworks.

Note that `multi_chunk_sendfile` and `multiproc*` test cases in
mptcp_data *may* require longer timeout than default[1].

Patch 1 is actually a fix for a pre-existing issues targeting net,
included here just for my convenience.

Patch 2 and 3 make the admission check much more strict for incoming
packets exceeding the memory limits, with some exception for fallback
sockets.
Patch 4 implements OoO queue pruning for MPTCP.
Finally patch 5 and 6 improve the MPTCP-level retransmission schema to
make recovery from memory pressure/after MPTCP-level drop significantly
faster.

[1] In my testing on v8 and v9 mptcp_data survived a few hundred
iterations with the default timeout. Some independent testing would be
appreciated.
---
v8 -> v9:
  - dropped already merged old patches 1-3
  - reworded commit message in patch 4

Paolo Abeni (6):
  mptcp: allow subflow rcv wnd to shrink
  mptcp: explicitly drop over memory limits
  mptcp: enforce hard limit on backlog flushing
  mptcp: implemented OoO queue pruning
  mptcp: move the retrans loop to a separate helper
  mptcp: let the retrans scheduler do its job.

 net/mptcp/mib.c      |   3 +
 net/mptcp/mib.h      |   3 +
 net/mptcp/options.c  |  35 +++++-
 net/mptcp/protocol.c | 247 +++++++++++++++++++++++++++++++------------
 4 files changed, 218 insertions(+), 70 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-05-27 10:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 10:45 Paolo Abeni [this message]
2026-05-27 10:45 ` [PATCH v9 mptcp-next 1/6] mptcp: allow subflow rcv wnd to shrink Paolo Abeni
2026-05-27 10:45 ` [PATCH v9 mptcp-next 2/6] mptcp: explicitly drop over memory limits Paolo Abeni
2026-05-28  7:42   ` Paolo Abeni
2026-05-28  8:21   ` Matthieu Baerts
2026-05-28  8:26     ` Paolo Abeni
2026-05-28  8:32       ` Matthieu Baerts
2026-05-28 15:16         ` Paolo Abeni
2026-05-27 10:45 ` [PATCH v9 mptcp-next 3/6] mptcp: enforce hard limit on backlog flushing Paolo Abeni
2026-05-27 10:45 ` [PATCH v9 mptcp-next 4/6] mptcp: implemented OoO queue pruning Paolo Abeni
2026-05-28  8:45   ` Matthieu Baerts
2026-05-28 16:23     ` Paolo Abeni
2026-05-27 10:45 ` [PATCH v9 mptcp-next 5/6] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-05-27 10:45 ` [PATCH v9 mptcp-next 6/6] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-05-28  7:45   ` Paolo Abeni
2026-05-28  8:57     ` Matthieu Baerts
2026-05-27 12:07 ` [PATCH v9 mptcp-next 0/6] mptcp: address stall under memory pressure 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.1779876523.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.