From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, matthieu.baerts@tessares.net,
mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/8] mptcp: TCP fallback for established connections
Date: Sat, 23 Apr 2022 11:00:12 +0000 [thread overview]
Message-ID: <165071161219.8812.1323328975738766476.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220422215543.545732-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 22 Apr 2022 14:55:35 -0700 you wrote:
> RFC 8684 allows some MPTCP connections to fall back to regular TCP when
> the MPTCP DSS checksum detects middlebox interference, there is only a
> single subflow, and there is no unacknowledged out-of-sequence
> data. When this condition is detected, the stack sends a MPTCP DSS
> option with an "infinite mapping" to signal that a fallback is
> happening, and the peers will stop sending MPTCP options in their TCP
> headers. The Linux MPTCP stack has not yet supported this type of
> fallback, instead closing the connection when the MPTCP checksum fails.
>
> [...]
Here is the summary with links:
- [net-next,1/8] mptcp: don't send RST for single subflow
https://git.kernel.org/netdev/net-next/c/1761fed25678
- [net-next,2/8] mptcp: add the fallback check
https://git.kernel.org/netdev/net-next/c/0348c690ed37
- [net-next,3/8] mptcp: track and update contiguous data status
https://git.kernel.org/netdev/net-next/c/0530020a7c8f
- [net-next,4/8] mptcp: infinite mapping sending
https://git.kernel.org/netdev/net-next/c/1e39e5a32ad7
- [net-next,5/8] mptcp: infinite mapping receiving
https://git.kernel.org/netdev/net-next/c/f8d4bcacff3b
- [net-next,6/8] mptcp: add mib for infinite map sending
https://git.kernel.org/netdev/net-next/c/104125b82e5c
- [net-next,7/8] mptcp: dump infinite_map field in mptcp_dump_mpext
https://git.kernel.org/netdev/net-next/c/d9fdd02d4265
- [net-next,8/8] selftests: mptcp: add infinite map mibs check
https://git.kernel.org/netdev/net-next/c/8bd03be3418c
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:[~2022-04-23 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 21:55 [PATCH net-next 0/8] mptcp: TCP fallback for established connections Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 1/8] mptcp: don't send RST for single subflow Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 2/8] mptcp: add the fallback check Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 3/8] mptcp: track and update contiguous data status Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 4/8] mptcp: infinite mapping sending Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 5/8] mptcp: infinite mapping receiving Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 6/8] mptcp: add mib for infinite map sending Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 7/8] mptcp: dump infinite_map field in mptcp_dump_mpext Mat Martineau
2022-04-22 21:55 ` [PATCH net-next 8/8] selftests: mptcp: add infinite map mibs check Mat Martineau
2022-04-23 11:00 ` 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=165071161219.8812.1323328975738766476.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--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