From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH v4 mptcp-next 0/3] mptcp: cg and backlog follow-up
Date: Fri, 14 Nov 2025 13:06:45 +0100 [thread overview]
Message-ID: <257ff01c-c236-406f-9c98-123d9b3aef46@kernel.org> (raw)
In-Reply-To: <cover.1763111767.git.pabeni@redhat.com>
Hi Paolo,
On 14/11/2025 10:17, Paolo Abeni wrote:
> This tries to fix the existing races in memcg accounting with the
> backlog.
>
> Only minor delta over v3: typos, build fix without CG, and reworded
> comments/commit messages.
Now in our tree:
New patches for t/upstream:
- f67fd656fe97: mptcp: grafting MPJ subflow earlier
- 36a8ca62b02d: "squashed" patch 2/3 in "mptcp: fix memcg accounting for
passive sockets"
- a3565f84e54f: "squashed" patch 3/3 in "mptcp: leverage the backlog for
RX packet processing"
- Results: 13d7de45372c..13cda072207e (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/c2eff70b71b8c42253db435d68374277502522e7/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2025-11-14 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 9:17 [PATCH v4 mptcp-next 0/3] mptcp: cg and backlog follow-up Paolo Abeni
2025-11-14 9:17 ` [PATCH v4 mptcp-next 1/3] mptcp: grafting MPJ subflow earlier Paolo Abeni
2025-11-14 9:17 ` [PATCH v4 mptcp-next 2/3] Squash-to: "mptcp: fix memcg accounting for passive sockets" Paolo Abeni
2025-11-14 9:17 ` [PATCH v4 mptcp-next 3/3] Squash-to: "mptcp: leverage the backlog for RX packet processing" Paolo Abeni
2025-11-14 10:30 ` [PATCH v4 mptcp-next 0/3] mptcp: cg and backlog follow-up MPTCP CI
2025-11-14 11:58 ` Matthieu Baerts
2025-11-14 12:06 ` 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=257ff01c-c236-406f-9c98-123d9b3aef46@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