From: Jakub Kicinski <kuba@kernel.org>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/6] mptcp: Path manager mode selection
Date: Fri, 29 Apr 2022 17:51:14 -0700 [thread overview]
Message-ID: <20220429175114.2500d3a9@kernel.org> (raw)
In-Reply-To: <23ff3b49-2563-1874-fa35-3af55d3088e7@linux.intel.com>
On Thu, 28 Apr 2022 20:39:01 -0700 (PDT) Mat Martineau wrote:
> Sure, no problem. If you'd prefer a pull request for this feature as a
> whole I could stage that.
>
> Here's a tag (note: do not merge this as-is, the committer ids and full
> history aren't suitable) ->
> https://github.com/multipath-tcp/mptcp_net-next/commits/netdev-review-userspace-path-manager
>
> The last 26 commits there cover the full userspace path manager kernel
> code, with the first 6 of those being this series.
>
> Userspace path managers makes use of generic netlink MPTCP events that
> have already been upstream for a while, and the full series adds four
> netlink commands for userspace:
>
> * MPTCP_PM_CMD_ANNOUNCE: advertise an address that's available for
> additional subflow connections.
>
> * MPTCP_PM_CMD_REMOVE: revoke an advertisement
>
> * MPTCP_PM_CMD_SUBFLOW_CREATE: initiate a new subflow on an existing MPTCP
> connection
>
> * MPTCP_PM_CMD_SUBFLOW_DESTROY: close a subflow on an existing MPTCP
> connection
>
> There's one commit for each command, each with an obvious title ("mptcp:
> netlink: Add MPTCP_PM_CMD_<name>")
Thanks for the explanation, applied!
next prev parent reply other threads:[~2022-04-30 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 22:49 [PATCH net-next 0/6] mptcp: Path manager mode selection Mat Martineau
2022-04-27 22:49 ` [PATCH net-next 1/6] mptcp: Remove redundant assignments in path manager init Mat Martineau
2022-04-27 22:49 ` [PATCH net-next 2/6] mptcp: Add a member to mptcp_pm_data to track kernel vs userspace mode Mat Martineau
2022-04-27 22:49 ` [PATCH net-next 3/6] mptcp: Bypass kernel PM when userspace PM is enabled Mat Martineau
2022-04-27 22:50 ` [PATCH net-next 4/6] mptcp: Make kernel path manager check for userspace-managed sockets Mat Martineau
2022-04-27 22:50 ` [PATCH net-next 5/6] mptcp: Add a per-namespace sysctl to set the default path manager type Mat Martineau
2022-04-27 22:50 ` [PATCH net-next 6/6] selftests: mptcp: Add tests for userspace PM type Mat Martineau
2022-04-29 1:57 ` [PATCH net-next 0/6] mptcp: Path manager mode selection Jakub Kicinski
2022-04-29 3:39 ` Mat Martineau
2022-04-30 0:51 ` Jakub Kicinski [this message]
2022-04-30 1:00 ` patchwork-bot+netdevbpf
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=20220429175114.2500d3a9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--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).