From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [MPTCP next v3 00/12] mptcp: receive path improvement
Date: Fri, 19 Sep 2025 23:13:15 +0200 [thread overview]
Message-ID: <4e5d00ca-1317-4f98-952b-e7ac058c52b7@kernel.org> (raw)
In-Reply-To: <cover.1758296923.git.pabeni@redhat.com>
Hi Paolo,
On 19/09/2025 17:53, Paolo Abeni wrote:
> This series includes several changes to the MPTCP RX path.
>
> The main goals are improving the RX performances _and_ increase the
> long term maintainability.
>
> Some changes reflects recent (or not so) improvements introduced in the
> TCP stack: patch 1, 2 and 3 are the MPTCP counter part of skb deferral
> free and auto-tuning improvements.
>
> Note that patch 3 could possibly fix issues/574, and overall such patch
> should protect from similar issues to arise in the future.
>
> All the others patches are aimed at introducing the socket backlog usage
> to process the packets received by the subflows while the msk socket is
> owned. That (almost completely) replace the processing currently
> happening in the mptcp_release_cb().
>
> The actual job is done in patch 10, while the others are cleanups needed
> to make the change tidy and more follow-up cleanups.
>
> Sharing earlier with known issues (at least on fallback socket) to raise
> awareness about this upcoming work.
> ---
> v2 -> v3:
> - (hopefully) addressed CI failures
Sadly, the CI doesn't seem that happy, but only in debug mode:
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/17863851247
If it is easier for you, I can already apply (and send to netdev?) some
of these patches? e.g. 1-7/12?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-09-19 21:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 15:53 [MPTCP next v3 00/12] mptcp: receive path improvement Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 01/12] mptcp: leverage skb deferral free Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 02/12] tcp: make tcp_rcvbuf_grow() accessible to mptcp code Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 03/12] mptcp: rcvbuf auto-tuning improvement Paolo Abeni
2025-09-19 21:10 ` Matthieu Baerts
2025-09-19 15:53 ` [MPTCP next v3 04/12] mptcp: introduce the mptcp_init_skb helper Paolo Abeni
2025-09-20 0:01 ` Geliang Tang
2025-09-22 10:44 ` Paolo Abeni
2025-09-20 0:03 ` Geliang Tang
2025-09-21 0:23 ` Geliang Tang
2025-09-21 0:48 ` Geliang Tang
2025-09-19 15:53 ` [MPTCP next v3 05/12] mptcp: remove unneeded mptcp_move_skb() Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 06/12] mptcp: factor out a basic skb coalesce helper Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 07/12] mptcp: minor move_skbs_to_msk() cleanup Paolo Abeni
2025-09-19 15:53 ` [MPTCP next v3 08/12] mptcp: cleanup fallback data fin reception Paolo Abeni
2025-09-20 0:04 ` Geliang Tang
2025-09-19 15:53 ` [MPTCP next v3 09/12] mptcp: cleanup fallback dummy mapping generation Paolo Abeni
2025-09-20 0:06 ` Geliang Tang
2025-09-21 1:01 ` Geliang Tang
2025-09-19 15:53 ` [MPTCP next v3 10/12] mptcp: leverage the sk backlog for RX packet processing Paolo Abeni
2025-09-20 0:09 ` Geliang Tang
2025-09-21 0:27 ` Geliang Tang
2025-09-19 15:53 ` [MPTCP next v3 11/12] mptcp: prevernt __mptcp_move_skbs() interfering with the fastpath Paolo Abeni
2025-09-21 0:27 ` Geliang Tang
2025-09-19 15:53 ` [MPTCP next v3 12/12] mptcp: borrow forward memory from subflow Paolo Abeni
2025-09-21 0:28 ` Geliang Tang
2025-09-19 18:36 ` [MPTCP next v3 00/12] mptcp: receive path improvement MPTCP CI
2025-09-19 21:13 ` Matthieu Baerts [this message]
2025-09-20 4:13 ` Geliang Tang
2025-09-20 4:15 ` Geliang Tang
2025-09-23 16:15 ` Paolo Abeni
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=4e5d00ca-1317-4f98-952b-e7ac058c52b7@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 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.