Re: [PATCH net-next 0/6] mptcp: Add full mesh path manager option

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue, 17 Aug 2021 15:07:21 -0700 you wrote:

The path manager in MPTCP controls the creation of additional subflows
after the initial connection is created. As each peer advertises
available endpoints with the ADD_ADDR MPTCP option, the recipient of
those advertisements must decide which subflows to create from the known
local and remote interfaces that are available for use by MPTCP.

The existing in-kernel path manager will create one additional subflow
when an ADD_ADDR is received, or a local address is newly configured for
MPTCP use. The maximum number of subflows has a configurable limit.

[...]

Here is the summary with links:
  - [net-next,1/6] mptcp: drop flags and ifindex arguments
    https://git.kernel.org/netdev/net-next/c/ee285257a9c1
  - [net-next,2/6] mptcp: remote addresses fullmesh
    https://git.kernel.org/netdev/net-next/c/2843ff6f36db
  - [net-next,3/6] mptcp: local addresses fullmesh
    https://git.kernel.org/netdev/net-next/c/1a0d6136c5f0
  - [net-next,4/6] selftests: mptcp: set and print the fullmesh flag
    https://git.kernel.org/netdev/net-next/c/371b90377e60
  - [net-next,5/6] selftests: mptcp: add fullmesh testcases
    https://git.kernel.org/netdev/net-next/c/4f49d63352da
  - [net-next,6/6] selftests: mptcp: delete uncontinuous removing ids
    https://git.kernel.org/netdev/net-next/c/f7713dd5d23a

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