mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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,
	geliangtang@xiaomi.com
Subject: Re: [PATCH net-next 0/6] mptcp: Add full mesh path manager option
Date: Wed, 18 Aug 2021 09:20:06 +0000	[thread overview]
Message-ID: <162927840633.7428.12959095508156490312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210817220727.192198-1-mathew.j.martineau@linux.intel.com>

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



      parent reply	other threads:[~2021-08-18  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 22:07 [PATCH net-next 0/6] mptcp: Add full mesh path manager option Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 1/6] mptcp: drop flags and ifindex arguments Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 2/6] mptcp: remote addresses fullmesh Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 3/6] mptcp: local " Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 4/6] selftests: mptcp: set and print the fullmesh flag Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 5/6] selftests: mptcp: add fullmesh testcases Mat Martineau
2021-08-17 22:07 ` [PATCH net-next 6/6] selftests: mptcp: delete uncontinuous removing ids Mat Martineau
2021-08-18  9: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=162927840633.7428.12959095508156490312.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=geliangtang@xiaomi.com \
    --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 \
    /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).