MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Cc: Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH mptcp-next 1/2] Squash to "mptcp: explicitly drop over memory limits"
Date: Fri, 31 Jul 2026 12:17:06 +0200	[thread overview]
Message-ID: <b5f74349-ab93-401a-9f90-a7bfc7ea4f1d@kernel.org> (raw)
In-Reply-To: <20260731-mptcp-squash-ooo-pruning-v1-1-a5f5115e1e24@kernel.org>

Hello,

On 31/07/2026 11:23, Matthieu Baerts (NGI0) wrote:
> Address comments from Clashiko [1]:
> 
> - mib: typo: "constrains" -> "constraints".
> 
> - mptcp_over_limit: precise it is not only 0-win, but retrans, dup or
>   old acks.
> 
> - mptcp_over_limit: bump LINUX_MIB_TCPRCVQDROP, as previously discussed
>   in [2].
> 
> Link: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260724-net-next-mptcp-oooq-pruning-v1-0-5dd4dec63a54%40kernel.org?part=3 [1]
> Link: https://lore.kernel.org/b5244dd4-205d-4abd-8ea5-fd879a97038f@redhat.com
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
>  net/mptcp/mib.h     | 2 +-
>  net/mptcp/options.c | 6 +++++-
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/net/mptcp/mib.h b/net/mptcp/mib.h
> index 18f35f7e0a2d..25f360724c57 100644
> --- a/net/mptcp/mib.h
> +++ b/net/mptcp/mib.h
> @@ -89,7 +89,7 @@ enum linux_mptcp_mib_field {
>  	MPTCP_MIB_FALLBACKFAILED,	/* Can't fallback due to msk status */
>  	MPTCP_MIB_WINPROBE,		/* MPTCP-level zero window probe */
>  	MPTCP_MIB_BACKLOGDROP,		/* Backlog over memory limit */
> -	MPTCP_MIB_RCVPRUNED,		/* Dropped due to memory constrains */
> +	MPTCP_MIB_RCVPRUNED,		/* Dropped due to memory constraints */
>  	MPTCP_MIB_OFO_PRUNED,		/* MPTCP-level OoO queue pruned */
>  	__MPTCP_MIB_MAX
>  };
> diff --git a/net/mptcp/options.c b/net/mptcp/options.c
> index d6b009319839..23503984a084 100644
> --- a/net/mptcp/options.c
> +++ b/net/mptcp/options.c
> @@ -1193,7 +1193,7 @@ static bool mptcp_over_limit(struct sock *sk, struct sock *ssk,
>  	if (likely(mem <= READ_ONCE(sk->sk_rcvbuf)))
>  		return false;
>  
> -	/* Avoid silently dropping pure acks, fin or zero win probes. */
> +	/* Avoid silently dropping pure acks, fin or already-acked segments. */
>  	if (TCP_SKB_CB(skb)->seq == TCP_SKB_CB(skb)->end_seq ||
>  	    TCP_SKB_CB(skb)->tcp_flags & TCPHDR_FIN ||
>  	    !after(TCP_SKB_CB(skb)->end_seq, tcp_sk(ssk)->rcv_nxt))
> @@ -1202,6 +1202,10 @@ static bool mptcp_over_limit(struct sock *sk, struct sock *ssk,
>  	/* Dropped due to memory constraints, schedule an ack. */
>  	inet_csk(ssk)->icsk_ack.pending |= ICSK_ACK_NOMEM | ICSK_ACK_NOW;
>  	inet_csk_schedule_ack(ssk);
> +
> +	/* In fallback mode: skb is dropped before the TCP recv queue. */
> +	MPTCP_INC_STATS(sock_net(sk), LINUX_MIB_TCPRCVQDROP);

Arf, it should be NET_INC_STATS(), not the MPTCP version: I changed to
LINUX_MIB_TCPRCVQDROP just before sending the patches, without checking
in between...

Sorry for the noise, v2 is coming.

> +
>  	return true;
>  }
>  
> 

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


  reply	other threads:[~2026-07-31 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  9:23 [PATCH mptcp-next 0/2] Squash to "mptcp: out-of-order queue pruning" Matthieu Baerts (NGI0)
2026-07-31  9:23 ` [PATCH mptcp-next 1/2] Squash to "mptcp: explicitly drop over memory limits" Matthieu Baerts (NGI0)
2026-07-31 10:17   ` Matthieu Baerts [this message]
2026-07-31  9:23 ` [PATCH mptcp-next 2/2] Squash to "mptcp: implemented OoO queue pruning" Matthieu Baerts (NGI0)
2026-07-31 10:07 ` [PATCH mptcp-next 0/2] Squash to "mptcp: out-of-order " 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=b5f74349-ab93-401a-9f90-a7bfc7ea4f1d@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