From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v12 mptcp-next 0/2] mptcp: address stall under memory pressure
Date: Wed, 3 Jun 2026 20:27:09 +1000 [thread overview]
Message-ID: <fe83c8c9-35bd-4e94-883b-3e141ebd41b8@kernel.org> (raw)
In-Reply-To: <cover.1780479980.git.pabeni@redhat.com>
Hi Paolo,
On 03/06/2026 19:47, Paolo Abeni wrote:
> 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
> sashiko feedback over the previous iteration (possible infinite rtx
> loop).
Thank you for the new version!
Now in our tree (applied before "mptcp: explicitly drop over memory
limits"):
New patches for t/upstream:
- be1684baf0a2: mptcp: move the retrans loop to a separate helper
- 9851d9d1f26c: mptcp: let the retrans scheduler do its job
- Results: bbaffa2dac1b..148c8fb6decf (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/9c934666a4f898f1271d5788617d3ccb1d5e600a/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-06-03 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 9:47 [PATCH v12 mptcp-next 0/2] mptcp: address stall under memory pressure Paolo Abeni
2026-06-03 9:47 ` [PATCH v12 mptcp-next 1/2] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-06-03 9:47 ` [PATCH v12 mptcp-next 2/2] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-06-03 10:27 ` Matthieu Baerts [this message]
2026-06-03 11:44 ` [PATCH v12 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=fe83c8c9-35bd-4e94-883b-3e141ebd41b8@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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.