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,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/8] mptcp: Improve use of backup subflows
Date: Sat, 14 Aug 2021 11:10:06 +0000 [thread overview]
Message-ID: <162893940609.15993.1576871199881701981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210813221548.111990-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 13 Aug 2021 15:15:40 -0700 you wrote:
> Multipath TCP combines multiple TCP subflows in to one stream, and the
> MPTCP-level socket must decide which subflow to use when sending (or
> resending) chunks of data. The choice of the "best" subflow to transmit
> on can vary depending on the priority (normal or backup) for each
> subflow and how well the subflow is performing.
>
> In order to improve MPTCP performance when some subflows are failing,
> this patch set changes how backup subflows are utilized and introduces
> tracking of "stale" subflows that are still connected but not making
> progress.
>
> [...]
Here is the summary with links:
- [net-next,1/8] mptcp: more accurate timeout
https://git.kernel.org/netdev/net-next/c/33d41c9cd74c
- [net-next,2/8] mptcp: less aggressive retransmission strategy
https://git.kernel.org/netdev/net-next/c/71b7dec27f34
- [net-next,3/8] mptcp: handle pending data on closed subflow
https://git.kernel.org/netdev/net-next/c/1e1d9d6f119c
- [net-next,4/8] mptcp: cleanup sysctl data and helpers
https://git.kernel.org/netdev/net-next/c/6da14d74e2bd
- [net-next,5/8] mptcp: faster active backup recovery
https://git.kernel.org/netdev/net-next/c/ff5a0b421cb2
- [net-next,6/8] mptcp: add mibs for stale subflows processing
https://git.kernel.org/netdev/net-next/c/fc1b4e3b6274
- [net-next,7/8] mptcp: backup flag from incoming MPJ ack option
https://git.kernel.org/netdev/net-next/c/0460ce229f5b
- [net-next,8/8] selftests: mptcp: add testcase for active-back
https://git.kernel.org/netdev/net-next/c/7d1e6f163904
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:[~2021-08-14 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 22:15 [PATCH net-next 0/8] mptcp: Improve use of backup subflows Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 1/8] mptcp: more accurate timeout Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 2/8] mptcp: less aggressive retransmission strategy Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 3/8] mptcp: handle pending data on closed subflow Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 4/8] mptcp: cleanup sysctl data and helpers Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 5/8] mptcp: faster active backup recovery Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 6/8] mptcp: add mibs for stale subflows processing Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 7/8] mptcp: backup flag from incoming MPJ ack option Mat Martineau
2021-08-13 22:15 ` [PATCH net-next 8/8] selftests: mptcp: add testcase for active-back Mat Martineau
2021-08-14 11:10 ` 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=162893940609.15993.1576871199881701981.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;
as well as URLs for NNTP newsgroup(s).