MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Cc: Mat Martineau <martineau@kernel.org>
Subject: Re: [PATCH v3 mptcp-next 2/7] mptcp: avoid unneeded subflow-level drops.
Date: Tue, 11 Nov 2025 19:43:46 +0100	[thread overview]
Message-ID: <e820a52a-7944-45b6-b3f1-4012a3856a4a@kernel.org> (raw)
In-Reply-To: <6af807a4d56bcac85d0908e30251ffa6d28ea38f.1762504059.git.pabeni@redhat.com>

Hi Paolo,

On 07/11/2025 09:32, Paolo Abeni wrote:
> The rcv window is shared among all the subflows. Currently, MPTCP sync
> the TCP-level rcv window with the MPTCP one at tcp_transmit_skb() time.
> 
> The above means that incoming data may sporadically observe outdated
> TCP-level rcv window and being wrongly dropped by TCP.
> 
> Address the issue checking for the edge condition before queuing the data
> at TCP level, and eventually syncing the rcv window as needed.
> 
> Note that the issue is actually present from the very first MPTCP
> implementation, but backports older than the blamed commit below will range
> from impossible to useless.

Thank you for this patch!

It looks good to me:

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

> Before:
> nstat >/dev/null ;sleep 1; nstat -z TcpExtBeyondWindow
> TcpExtBeyondWindow              14                 0.0
> 
> After:
> nstat >/dev/null ;sleep 1; nstat -z TcpExtBeyondWindow
> TcpExtBeyondWindow              0                  0.0
Should we eventually track this MIB counter in mptcp_connect.sh?

> Fixes: fa3fe2b15031 ("mptcp: track window announced to peer")

While there are still discussions on patch 6/7, to ease things, I
suggest already applying only this patch in our tree (fixes for -net),
the only material for 'net' from what I understood.

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


  reply	other threads:[~2025-11-11 18:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07  8:32 [PATCH v3 mptcp-next 0/7] mptcp: autotune related improvement Paolo Abeni
2025-11-07  8:32 ` [PATCH v3 mptcp-next 1/7] trace: mptcp: add mptcp_rcvbuf_grow tracepoint Paolo Abeni
2025-11-07  8:32 ` [PATCH v3 mptcp-next 2/7] mptcp: avoid unneeded subflow-level drops Paolo Abeni
2025-11-11 18:43   ` Matthieu Baerts [this message]
2025-11-11 18:53     ` Matthieu Baerts
2025-11-07  8:32 ` [PATCH v3 mptcp-next 3/7] mptcp: fix receive space timestamp initialization Paolo Abeni
2025-11-07  8:32 ` [PATCH v3 mptcp-next 4/7] mptcp: consolidate rcv space init Paolo Abeni
2025-11-07  8:32 ` [PATCH v3 mptcp-next 5/7] mptcp: better rcv space initialization Paolo Abeni
2025-11-07  8:32 ` [PATCH v3 mptcp-next 6/7] mptcp: better mptcp-level RTT estimator Paolo Abeni
2025-11-11  1:56   ` Mat Martineau
2025-11-07  8:32 ` [PATCH v3 mptcp-next 7/7] mptcp: add receive queue awareness in tcp_rcv_space_adjust() Paolo Abeni
2025-11-07  9:56 ` [PATCH v3 mptcp-next 0/7] mptcp: autotune related improvement MPTCP CI

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=e820a52a-7944-45b6-b3f1-4012a3856a4a@kernel.org \
    --to=matttbe@kernel.org \
    --cc=martineau@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