|
|
Subscribe / Log in / New account

Upstreaming multipath TCP

Upstreaming multipath TCP

Posted Sep 27, 2019 17:42 UTC (Fri) by raven667 (subscriber, #5198)
In reply to: Upstreaming multipath TCP by kevincox
Parent article: Upstreaming multipath TCP

I dunno if this would make sense to implement in the OS kernel, but you could build this exact behavior into an application by having an anycast service that just returns the IP (and port?) you want the client to load balance to, followed by an MTCP connection to that service. One could probably make that into a client library and server daemon to make it easy to be integrated into any software that wanted to behave this way but the OS provides all the primitives necessary to have this work, and there probably isn't any benefit in abstracting that away into the kernel as opposed to having userspace control all the knobs and build on top.


to post comments

Upstreaming multipath TCP

Posted Sep 27, 2019 17:47 UTC (Fri) by kevincox (subscriber, #93938) [Link]

You can definitely do it this way. DNS is commonly used as that anycast service. However there are a number of reasons this isn't quite ideal including staleness or added latency.

Doing it via MPTCP means that you don't have any added latency in exchange for no guarantee that the "connection" doesn't get migrated to a different target before the "handover" to the server IP.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds