From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-next 0/7] mptcp: address stall under memory pressure
Date: Fri, 7 Aug 2026 13:45:58 +0200 [thread overview]
Message-ID: <6aa24894-a3c2-4c86-912a-0c17d6048433@kernel.org> (raw)
In-Reply-To: <cover.1786026372.git.pabeni@redhat.com>
Hi Paolo,
On 06/08/2026 16:45, Paolo Abeni wrote:
> This *should* address opus-5 feedback, as observed upstream.
Thank you for the new version, and your patience with AI reviews!
Hopefully opus-5 will not be even more picky!
This new version looks good to me:
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
New patches for t/upstream:
- b03efee5f28b: mptcp: move the retrans loop to a separate helper
- 23b698046768: mptcp: move the stale logic out of retrans scheduler
- 1a2614f8a410: mptcp: let the retrans scheduler do its job
- 568cc4fa11f2: mptcp: explicitly drop over memory limits
- c29573ac23e6: mptcp: enforce hard limit on backlog flushing
- e76d982954d3: mptcp: avoid code duplication in __mptcp_move_skb()
- b746103fb892: mptcp: implemented OoO queue pruning
- Results: 775addc43266..7bf94a8339a9 (export)
(+ Geliang's fixes for the BPF selftests)
Tests are now in progress:
- export: https://github.com/multipath-tcp/mptcp_net-next/commit/58dcc35549b1dfcf3d689fc5e163a25fb11a335c/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-08-07 11:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 14:45 [PATCH v2 mptcp-next 0/7] mptcp: address stall under memory pressure Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 1/7] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 2/7] mptcp: move the stale logic out of retrans scheduler Paolo Abeni
2026-08-06 16:41 ` Paolo Abeni
2026-08-06 16:45 ` Matthieu Baerts
2026-08-06 14:45 ` [PATCH v2 mptcp-next 3/7] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 4/7] mptcp: explicitly drop over memory limits Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 5/7] mptcp: enforce hard limit on backlog flushing Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 6/7] mptcp: avoid code duplication in __mptcp_move_skb() Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 7/7] mptcp: implemented OoO queue pruning Paolo Abeni
2026-08-06 16:42 ` Paolo Abeni
2026-08-06 16:46 ` Matthieu Baerts
2026-08-08 2:31 ` Geliang Tang
2026-08-08 16:34 ` Matthieu Baerts
2026-08-10 10:47 ` Paolo Abeni
2026-08-07 11:45 ` Matthieu Baerts [this message]
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=6aa24894-a3c2-4c86-912a-0c17d6048433@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox