From: Christoph Paasch <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] Userspace Path Manager Draft
Date: Fri, 23 Mar 2018 16:14:43 +0000 [thread overview]
Message-ID: <20180323161443.GA54772@MacBook-Pro-6.local> (raw)
In-Reply-To: 20180322204109.GA29903@pride
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
Hello Stephen,
On 22/03/18 - 13:41:09, Stephen Brennan wrote:
> Hello everyone,
>
> I did not sit in on the meeting since I am feeling sick, so I haven't had a
> chance to see whether this is actually a useful contribution. However, over
> the past week I've been tinkering with the userspace Generic Netlink
> libraries, getting a prototype of what a userspace path manager framework
> could look like.
Awesome!
> My current idea is built so that it could support multiple path managers,
> implemented as shared libraries, which are dynamically loaded at runtime.
> There would need to be some policy or logic to decide which connections are
> assigned to which path manager; I haven't fleshed out what that looks like.
I see, kinda like a pluggable path-manager in user-space, right?
I like that idea.
> Without an exact API reference, I simply based the API on what Ossama
> proposed last week. To test, I created a dummy kernel path manager which
> sends empty Netlink messages. It seems to work so far.
>
> I don't know if those working on the Netlink API have been developing
> userspace tooling in parallel, but if not, maybe this will be useful.
I think it will be very useful. I'm sure that Matthieu has also a
path-manager daemon. But having an additional one with other use-cases and
implementations in mind will allow to validate that the netlink API works
for more diverse use-cases.
> You
> can find it here:
>
> https://github.com/brenns10/pathmand
I will take a look at it.
Cheers,
Christoph
next reply other threads:[~2018-03-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 16:14 Christoph Paasch [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-22 20:41 [MPTCP] Userspace Path Manager Draft Stephen Brennan
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=20180323161443.GA54772@MacBook-Pro-6.local \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.