From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: edumazet@google.com, kuniyu@google.com, pabeni@redhat.com,
willemb@google.com, davem@davemloft.net, kuba@kernel.org,
horms@kernel.org, dsahern@kernel.org, martineau@kernel.org,
geliang@kernel.org, peter.krystad@linux.intel.com, fw@strlen.de,
cpaasch@apple.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mptcp@lists.linux.dev,
dcaratti@redhat.com
Subject: Re: [PATCH net-next 00/14] mptcp: memcg accounting for passive sockets & backlog processing
Date: Tue, 25 Nov 2025 04:40:23 +0000 [thread overview]
Message-ID: <176404562300.189804.16757204264695752077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251121-net-next-mptcp-memcg-backlog-imp-v1-0-1f34b6c1e0b1@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 21 Nov 2025 18:01:59 +0100 you wrote:
> This series is split in two: the 4 first patches are linked to memcg
> accounting for passive sockets, and the rest introduce the backlog
> processing. They are sent together, because the first one appeared to be
> needed to get the second one fully working.
>
> The second part includes RX path improvement built around backlog
> processing. The main goals are improving the RX performances _and_
> increase the long term maintainability.
>
> [...]
Here is the summary with links:
- [net-next,01/14] net: factor-out _sk_charge() helper
https://git.kernel.org/netdev/net-next/c/075b19c211df
- [net-next,02/14] mptcp: factor-out cgroup data inherit helper
https://git.kernel.org/netdev/net-next/c/bd92dd8e03d9
- [net-next,03/14] mptcp: grafting MPJ subflow earlier
https://git.kernel.org/netdev/net-next/c/e777a7fb06b1
- [net-next,04/14] mptcp: fix memcg accounting for passive sockets
https://git.kernel.org/netdev/net-next/c/68c7c3867145
- [net-next,05/14] mptcp: cleanup fallback data fin reception
https://git.kernel.org/netdev/net-next/c/85f22b8e1e9d
- [net-next,06/14] mptcp: cleanup fallback dummy mapping generation
https://git.kernel.org/netdev/net-next/c/2834f8edd74d
- [net-next,07/14] mptcp: ensure the kernel PM does not take action too late
https://git.kernel.org/netdev/net-next/c/2ca1b8926fda
- [net-next,08/14] mptcp: do not miss early first subflow close event notification
https://git.kernel.org/netdev/net-next/c/48a395605e08
- [net-next,09/14] mptcp: make mptcp_destroy_common() static
https://git.kernel.org/netdev/net-next/c/9d8295960300
- [net-next,10/14] mptcp: drop the __mptcp_data_ready() helper
https://git.kernel.org/netdev/net-next/c/38a4a469c850
- [net-next,11/14] mptcp: handle first subflow closing consistently
https://git.kernel.org/netdev/net-next/c/0eeb372deebc
- [net-next,12/14] mptcp: borrow forward memory from subflow
https://git.kernel.org/netdev/net-next/c/9db5b3cec4ec
- [net-next,13/14] mptcp: introduce mptcp-level backlog
https://git.kernel.org/netdev/net-next/c/ee458a3f314e
- [net-next,14/14] mptcp: leverage the backlog for RX packet processing
https://git.kernel.org/netdev/net-next/c/6228efe0cc01
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:[~2025-11-25 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 17:01 [PATCH net-next 00/14] mptcp: memcg accounting for passive sockets & backlog processing Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 01/14] net: factor-out _sk_charge() helper Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 02/14] mptcp: factor-out cgroup data inherit helper Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 03/14] mptcp: grafting MPJ subflow earlier Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 04/14] mptcp: fix memcg accounting for passive sockets Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 05/14] mptcp: cleanup fallback data fin reception Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 06/14] mptcp: cleanup fallback dummy mapping generation Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 07/14] mptcp: ensure the kernel PM does not take action too late Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 08/14] mptcp: do not miss early first subflow close event notification Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 09/14] mptcp: make mptcp_destroy_common() static Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 10/14] mptcp: drop the __mptcp_data_ready() helper Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 11/14] mptcp: handle first subflow closing consistently Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 12/14] mptcp: borrow forward memory from subflow Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 13/14] mptcp: introduce mptcp-level backlog Matthieu Baerts (NGI0)
2025-11-21 17:02 ` [PATCH net-next 14/14] mptcp: leverage the backlog for RX packet processing Matthieu Baerts (NGI0)
2025-11-25 4: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=176404562300.189804.16757204264695752077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--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=peter.krystad@linux.intel.com \
--cc=willemb@google.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