summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2025-11-21 20:02:12 +0300
committerJakub Kicinski <kuba@kernel.org>2025-11-25 06:49:43 +0300
commitee458a3f314e9c669ddd227bf5ab08354d9e75cc (patch)
treed13c273353e0751d1e9de5f0868f13f5b6f07416 /tools/lib/python
parent9db5b3cec4ec1c0cd3239689f5c8653d691a1754 (diff)
downloadlinux-ee458a3f314e9c669ddd227bf5ab08354d9e75cc.tar.xz
mptcp: introduce mptcp-level backlog
We are soon using it for incoming data processing. MPTCP can't leverage the sk_backlog, as the latter is processed before the release callback, and such callback for MPTCP releases and re-acquire the socket spinlock, breaking the sk_backlog processing assumption. Add a skb backlog list inside the mptcp sock struct, and implement basic helper to transfer packet to and purge such list. Packets in the backlog are memory accounted and still use the incoming subflow receive memory, to allow back-pressure. The backlog size is implicitly bounded to the sum of subflows rcvbuf. When a subflow is closed, references from the backlog to such sock are removed. No packet is currently added to the backlog, so no functional changes intended here. Signed-off-by: Paolo Abeni <pabeni@redhat.com> Reviewed-by: Mat Martineau <martineau@kernel.org> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> Link: https://patch.msgid.link/20251121-net-next-mptcp-memcg-backlog-imp-v1-13-1f34b6c1e0b1@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions