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
Subject: Re: [PATCH net-next 0/6] MPTCP: Allow initial subflow to be disconnected
Date: Wed, 31 Mar 2021 00:50:09 +0000 [thread overview]
Message-ID: <161715180983.15741.2464125249248249842.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210331000856.117636-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 17:08:50 -0700 you wrote:
> An MPTCP connection is aggregated from multiple TCP subflows, and can
> involve multiple IP addresses on either peer. The addresses used in the
> initial subflow connection are assigned address id 0 on each side of the
> link. More addresses can be added and shared with the peer using address
> IDs of 1 or larger. MPTCP in Linux shares non-zero address IDs across
> all MPTCP connections in a net namespace, which allows userspace to
> manage subflow connections across a number of sockets. However, this
> makes the address with id 0 a special case, since the IP address
> associated with id 0 is potentially different for each socket.
>
> [...]
Here is the summary with links:
- [net-next,1/6] mptcp: remove all subflows involving id 0 address
https://git.kernel.org/netdev/net-next/c/774c8a8dcb3c
- [net-next,2/6] mptcp: unify RM_ADDR and RM_SUBFLOW receiving
https://git.kernel.org/netdev/net-next/c/9f12e97bf16c
- [net-next,3/6] mptcp: remove id 0 address
https://git.kernel.org/netdev/net-next/c/740d798e8767
- [net-next,4/6] selftests: mptcp: avoid calling pm_nl_ctl with bad IDs
https://git.kernel.org/netdev/net-next/c/6254ad408820
- [net-next,5/6] selftests: mptcp: add addr argument for del_addr
https://git.kernel.org/netdev/net-next/c/2d121c9a882a
- [net-next,6/6] selftests: mptcp: remove id 0 address testcases
https://git.kernel.org/netdev/net-next/c/5e287fe76149
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-03-31 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 0:08 [PATCH net-next 0/6] MPTCP: Allow initial subflow to be disconnected Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 1/6] mptcp: remove all subflows involving id 0 address Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 2/6] mptcp: unify RM_ADDR and RM_SUBFLOW receiving Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 3/6] mptcp: remove id 0 address Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 4/6] selftests: mptcp: avoid calling pm_nl_ctl with bad IDs Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 5/6] selftests: mptcp: add addr argument for del_addr Mat Martineau
2021-03-31 0:08 ` [PATCH net-next 6/6] selftests: mptcp: remove id 0 address testcases Mat Martineau
2021-03-31 0:50 ` 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=161715180983.15741.2464125249248249842.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 \
/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).