From: Jakub Kicinski <kuba@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH net-next 0/5] mptcp: out-of-order queue pruning
Date: Mon, 27 Jul 2026 17:58:20 -0700 [thread overview]
Message-ID: <20260727175820.593c039e@kernel.org> (raw)
In-Reply-To: <20260724-net-next-mptcp-oooq-pruning-v1-0-5dd4dec63a54@kernel.org>
On Fri, 24 Jul 2026 16:02:12 +0200 Matthieu Baerts (NGI0) wrote:
> Under memory pressure, a pruning of the MPTCP-level OoO queue might be
> required as last resort, to avoid too long recoveries, or even stalls.
> Geliang and Gang managed to reproduce this behaviour, and Paolo
> improved the situation thanks to the following patches:
>
> - Patches 1-2: improve the MPTCP-level retransmission schema to make
> recoveries from memory pressure/after MPTCP-level drop significantly
> faster.
>
> - Patches 2-3: make the admission check way stricter for incoming
> packets exceeding the memory limits, with some exceptions for fallback
> sockets.
>
> - Patch 5: implement OoO queue pruning for MPTCP.
Clashiko complains about a typo and has some suggestions which are
marked as Low but potentially worth addressing (stats naming?)
Please LMK if you completely disagree
--
pw-bot: cr
prev parent reply other threads:[~2026-07-28 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 14:02 [PATCH net-next 0/5] mptcp: out-of-order queue pruning Matthieu Baerts (NGI0)
2026-07-24 14:02 ` [PATCH net-next 1/5] mptcp: move the retrans loop to a separate helper Matthieu Baerts (NGI0)
2026-07-24 14:02 ` [PATCH net-next 2/5] mptcp: let the retrans scheduler do its job Matthieu Baerts (NGI0)
2026-07-24 14:02 ` [PATCH net-next 3/5] mptcp: explicitly drop over memory limits Matthieu Baerts (NGI0)
2026-07-27 9:07 ` Paolo Abeni
2026-07-24 14:02 ` [PATCH net-next 4/5] mptcp: enforce hard limit on backlog flushing Matthieu Baerts (NGI0)
2026-07-24 14:02 ` [PATCH net-next 5/5] mptcp: implemented OoO queue pruning Matthieu Baerts (NGI0)
2026-07-28 0:58 ` Jakub Kicinski [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=20260727175820.593c039e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangang@kylinos.cn \
/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.