MPTCP Linux Development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, dsahern@kernel.org, martineau@kernel.org,
	geliang@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, mptcp@lists.linux.dev,
	rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/4] tcp: fix receive autotune again
Date: Thu, 30 Oct 2025 00:40:28 +0000	[thread overview]
Message-ID: <176178482800.3264893.3137378286090520073.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251028-net-tcp-recv-autotune-v3-0-74b43ba4c84c@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 28 Oct 2025 12:57:58 +0100 you wrote:
> Neal Cardwell found that recent kernels were having RWIN limited
> issues, even when net.ipv4.tcp_rmem[2] was set to a very big value like
> 512MB.
> 
> He suspected that tcp_stream default buffer size (64KB) was triggering
> heuristic added in ea33537d8292 ("tcp: add receive queue awareness
> in tcp_rcv_space_adjust()").
> 
> [...]

Here is the summary with links:
  - [net,v3,1/4] mptcp: fix subflow rcvbuf adjust
    https://git.kernel.org/netdev/net/c/a6f0459aadf1
  - [net,v3,2/4] trace: tcp: add three metrics to trace_tcp_rcvbuf_grow()
    https://git.kernel.org/netdev/net/c/24990d89c23d
  - [net,v3,3/4] tcp: add newval parameter to tcp_rcvbuf_grow()
    https://git.kernel.org/netdev/net/c/b1e014a1f327
  - [net,v3,4/4] tcp: fix too slow tcp_rcvbuf_grow() action
    https://git.kernel.org/netdev/net/c/aa251c84636c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-10-30  0:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 11:57 [PATCH net v3 0/4] tcp: fix receive autotune again Matthieu Baerts (NGI0)
2025-10-28 11:57 ` [PATCH net v3 1/4] mptcp: fix subflow rcvbuf adjust Matthieu Baerts (NGI0)
2025-10-28 11:58 ` [PATCH net v3 2/4] trace: tcp: add three metrics to trace_tcp_rcvbuf_grow() Matthieu Baerts (NGI0)
2025-10-29 13:41   ` Neal Cardwell
2025-10-28 11:58 ` [PATCH net v3 3/4] tcp: add newval parameter to tcp_rcvbuf_grow() Matthieu Baerts (NGI0)
2025-10-29 13:42   ` Neal Cardwell
2025-10-28 11:58 ` [PATCH net v3 4/4] tcp: fix too slow tcp_rcvbuf_grow() action Matthieu Baerts (NGI0)
2025-10-29 13:42   ` Neal Cardwell
2025-10-30  0:40 ` patchwork-bot+netdevbpf [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=176178482800.3264893.3137378286090520073.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=matttbe@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    /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