All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v10 mptcp-next 0/3] mptcp: address stall under memory pressure
Date: Fri, 29 May 2026 12:44:28 +0200	[thread overview]
Message-ID: <cover.1780049797.git.pabeni@redhat.com> (raw)

This brings (hopefully) the final bits required to address the
data transfer stall reported by Geliang and Gang 

Patch 1 is a mostly cosmetic change over a previously accepted patch,
while patch 2 and 3 improves mptcp retranmission to make them reliable:
pruning can require some of them.

The main change over the previous iteration is in patch 3, addressing
sashiko feedback over the previous iteration (missing timer reschedule
in some corner cases).

Paolo Abeni (3):
  Squash-to: "mptcp: implemented OoO queue pruning"
  mptcp: move the retrans loop to a separate helper
  mptcp: let the retrans scheduler do its job.

 net/mptcp/protocol.c | 177 ++++++++++++++++++++++++++++++-------------
 1 file changed, 123 insertions(+), 54 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-05-29 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 10:44 Paolo Abeni [this message]
2026-05-29 10:44 ` [PATCH v10 mptcp-next 1/3] Squash-to: "mptcp: implemented OoO queue pruning" Paolo Abeni
2026-05-30  8:52   ` Matthieu Baerts
2026-05-29 10:44 ` [PATCH v10 mptcp-next 2/3] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-05-29 10:44 ` [PATCH v10 mptcp-next 3/3] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-05-29 13:27   ` Geliang Tang
2026-05-29 14:14     ` Paolo Abeni
2026-05-29 14:41       ` Paolo Abeni
2026-05-29 17:04       ` Paolo Abeni
2026-05-30  4:23         ` Geliang Tang
2026-05-29 12:00 ` [PATCH v10 mptcp-next 0/3] 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.1780049797.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.