All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [MPTCP next v3 03/12] mptcp: rcvbuf auto-tuning improvement
Date: Fri, 19 Sep 2025 23:10:01 +0200	[thread overview]
Message-ID: <2f3d59ef-b909-4149-8c94-d014fa2ff543@kernel.org> (raw)
In-Reply-To: <3b9f144fd4df4c02550946d4208a0ede8e776526.1758296923.git.pabeni@redhat.com>

Hi Paolo,

On 19/09/2025 17:53, Paolo Abeni wrote:
> Apply to the MPTCP auto-tuning the same improvements introduced for the
> TCP protocol by the merge commit 2da35e4b4df9 ("Merge branch
> 'tcp-receive-side-improvements'").
> 
> The main difference is that TCP subflow and the main MPTCP socket need
> to account separately for OoO: MPTCP does not care for TCP-level OoO
> and vice versa, as a consequence do not reflect MPTCP-level rcvbuf
> increase due to OoO packets at the subflow level.
> 
> This refeactor additionally allow dropping the msk receive buffer update
> at receive time, as the latter only intended to cope with subflow receive
> buffer increase due to OoO packets.
> 
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/487
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/559
> Reviewed-by: Geliang Tang <geliang@kernel.org>
> Tested-by: Geliang Tang <geliang@kernel.org>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> v2 -> v3:
>   - copy tcp_rcvbuf_grow() implementation, verbatim
>   - intentionally omitted Mat's tag due to the many changes

Thank you for the v3, that's easier to spot the differences now!

Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-09-19 21:10 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 [this message]
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
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=2f3d59ef-b909-4149-8c94-d014fa2ff543@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.