From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, yangang@kylinos.cn
Subject: Re: [PATCH net-next v3 0/7] mptcp: out-of-order queue pruning
Date: Wed, 12 Aug 2026 01:40:41 +0000 [thread overview]
Message-ID: <178649884163.1230679.9378736754022898187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807-net-next-mptcp-oooq-pruning-v3-0-dbc1eb853cc3@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 07 Aug 2026 15:49:00 +0200 you 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-3: improve the MPTCP-level retransmission schema to make
> recoveries from memory pressure/after MPTCP-level drop significantly
> faster.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/7] mptcp: move the retrans loop to a separate helper
https://git.kernel.org/netdev/net-next/c/789e6a844b51
- [net-next,v3,2/7] mptcp: move the stale logic out of retrans scheduler
https://git.kernel.org/netdev/net-next/c/6cafe51e0f98
- [net-next,v3,3/7] mptcp: let the retrans scheduler do its job
https://git.kernel.org/netdev/net-next/c/96d846e3e2a7
- [net-next,v3,4/7] mptcp: explicitly drop over memory limits
https://git.kernel.org/netdev/net-next/c/e0e4d56b0505
- [net-next,v3,5/7] mptcp: enforce hard limit on backlog flushing
https://git.kernel.org/netdev/net-next/c/b1224c4b40f6
- [net-next,v3,6/7] mptcp: avoid code duplication in __mptcp_move_skb()
https://git.kernel.org/netdev/net-next/c/996643574cc8
- [net-next,v3,7/7] mptcp: implemented OoO queue pruning
https://git.kernel.org/netdev/net-next/c/e468d371180d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-12 1:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 13:49 [PATCH net-next v3 0/7] mptcp: out-of-order queue pruning Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 1/7] mptcp: move the retrans loop to a separate helper Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 2/7] mptcp: move the stale logic out of retrans scheduler Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 3/7] mptcp: let the retrans scheduler do its job Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 4/7] mptcp: explicitly drop over memory limits Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 5/7] mptcp: enforce hard limit on backlog flushing Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 6/7] mptcp: avoid code duplication in __mptcp_move_skb() Matthieu Baerts (NGI0)
2026-08-07 13:49 ` [PATCH net-next v3 7/7] mptcp: implemented OoO queue pruning Matthieu Baerts (NGI0)
2026-08-12 11:39 ` Eric Dumazet
2026-08-10 9:53 ` [PATCH net-next v3 0/7] mptcp: out-of-order " Paolo Abeni
2026-08-10 10:57 ` Matthieu Baerts
2026-08-12 1:40 ` patchwork-bot+netdevbpf [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=178649884163.1230679.9378736754022898187.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@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.