From: patchwork-bot+netdevbpf@kernel•org
To: Matthieu Baerts <matthieu.baerts@tessares•net>
Cc: mptcp@lists•linux.dev, edumazet@google•com, davem@davemloft•net,
kuba@kernel•org, pabeni@redhat•com, martineau@kernel•org,
soheil@google•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH net-next] mptcp: fix rcv buffer auto-tuning
Date: Tue, 25 Jul 2023 00:20:21 +0000 [thread overview]
Message-ID: <169024442128.15014.7119910740780685151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230720-upstream-net-next-20230720-mptcp-fix-rcv-buffer-auto-tuning-v1-1-175ef12b8380@tessares.net>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 20 Jul 2023 20:47:50 +0200 you wrote:
> From: Paolo Abeni <pabeni@redhat•com>
>
> The MPTCP code uses the assumption that the tcp_win_from_space() helper
> does not use any TCP-specific field, and thus works correctly operating
> on an MPTCP socket.
>
> The commit dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale")
> broke such assumption, and as a consequence most MPTCP connections stall
> on zero-window event due to auto-tuning changing the rcv buffer size
> quite randomly.
>
> [...]
Here is the summary with links:
- [net-next] mptcp: fix rcv buffer auto-tuning
https://git.kernel.org/netdev/net-next/c/b8dc6d6ce931
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-25 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 18:47 [PATCH net-next] mptcp: fix rcv buffer auto-tuning Matthieu Baerts
2023-07-20 19:07 ` Eric Dumazet
2023-07-20 19:14 ` Soheil Hassas Yeganeh
2023-07-25 0:20 ` 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=169024442128.15014.7119910740780685151.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=martineau@kernel$(echo .)org \
--cc=matthieu.baerts@tessares$(echo .)net \
--cc=mptcp@lists$(echo .)linux.dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=soheil@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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