From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v11 mptcp-next 0/2] mptcp: address stall under memory pressure
Date: Sat, 30 May 2026 16:59:47 +0200 [thread overview]
Message-ID: <cover.1780152380.git.pabeni@redhat.com> (raw)
This brings (hopefully) the final bits required to address the
data transfer stall reported by Geliang and Gang
This series improves mptcp retranmission to make them reliable:
pruning can require some of them.
The only change over the previous iteration is in patch 2, addressing
Geliang and sashiko feedback over the previous iteration (bad WARN
condition).
Paolo Abeni (2):
mptcp: move the retrans loop to a separate helper
mptcp: let the retrans scheduler do its job.
net/mptcp/protocol.c | 156 +++++++++++++++++++++++++++++++------------
1 file changed, 112 insertions(+), 44 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-30 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 14:59 Paolo Abeni [this message]
2026-05-30 14:59 ` [PATCH v11 mptcp-next 1/2] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-05-30 14:59 ` [PATCH v11 mptcp-next 2/2] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-05-30 16:28 ` [PATCH v11 mptcp-next 0/2] 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.1780152380.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.