3 ms·

Not sure, there's no indication that I could find of a roadmap to merge on the Linux MultiPath TCP web site: http://multipath-tcp.org/ http://multipath-tcp.org/

by lambda 13y ago

microcolonel 13y ago
“The current implementation of Multipath TCP in the Linux kernel supports RFC6824 and includes this fallback mechanism.” - [About Measures][0] 0: http://multipath-tcp.org/pmwiki.php/Users/AboutMeasures http://multipath-tcp.org/pmwiki.php/Users/AboutMeasures Please don't say things so scary without looking into it.
- lambda 13y ago
  When they say that, they mean in their fork of the Linux kernel: https://github.com/multipath-tcp/mptcp https://github.com/multipath-tcp/mptcp not in the official upstream kernel from Linus https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.... nor any of the mainstream distro kernels. You can check this for yourself. Just take a look for the MPTCP patches in Linus's kernel. You won't find them. Here's my kernel git repo; origin is Linus's repo, mptcp is the MPTCP development repo: $ git log --pretty=oneline origin/master..mptcp/mptcp_v0.87 | wc -l 2841 As you can see, there are 2841 patches in the mptcp_v0.87 branch that are not in the kernel repo, all the way back to the original shim6 patch that was used to start building MPTCP on top of shim6, which was a proposal for multi-homed IPv6 (MPTCP now works on top of IPv4 as well). Note that when you look at the "installing on Linux" instructions, they mention running it in a virtual machine. This is not terribly uncommon for an ambitious research effort; work on an out of tree fork for a while, and then when it's ready, propose it for inclusion into the upstream kernel. For a recent example, see Bcache http://bcache.evilpiepirate.org/ http://bcache.evilpiepirate.org/, which was developed out of tree for several years before being merged a few months ago. > Please don't say things so scary without looking into it. Why do you find this scary? And why do you think that I didn't look into this?
  - microcolonel 13y ago
    Ahh, the way you said it made it sound like the first bit was you talking out your ass, assuming that they hadn't merged any of their work by a few pages on their site. I am currently on a very restricted link, so I was not able to check the commit logs.

Not sure, there's no indication that I could find of a roadmap to merge on the Linux MultiPath TCP web site: http://multipath-tcp.org/ http://multipath-tcp.org/

by lambda 13y ago

Not sure, there's no indication that I could find of a roadmap to merge on the Linux MultiPath TCP web site: http://multipath-tcp.org/ http://multipath-tcp.org/

microcolonel 13y ago

“The current implementation of Multipath TCP in the Linux kernel supports RFC6824 and includes this fallback mechanism.” - [About Measures][0] 0: http://multipath-tcp.org/pmwiki.php/Users/AboutMeasures http://multipath-tcp.org/pmwiki.php/Users/AboutMeasures Please don't say things so scary without looking into it.

lambda 13y ago
When they say that, they mean in their fork of the Linux kernel: https://github.com/multipath-tcp/mptcp https://github.com/multipath-tcp/mptcp not in the official upstream kernel from Linus https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.... nor any of the mainstream distro kernels. You can check this for yourself. Just take a look for the MPTCP patches in Linus's kernel. You won't find them. Here's my kernel git repo; origin is Linus's repo, mptcp is the MPTCP development repo: $ git log --pretty=oneline origin/master..mptcp/mptcp_v0.87 | wc -l 2841 As you can see, there are 2841 patches in the mptcp_v0.87 branch that are not in the kernel repo, all the way back to the original shim6 patch that was used to start building MPTCP on top of shim6, which was a proposal for multi-homed IPv6 (MPTCP now works on top of IPv4 as well). Note that when you look at the "installing on Linux" instructions, they mention running it in a virtual machine. This is not terribly uncommon for an ambitious research effort; work on an out of tree fork for a while, and then when it's ready, propose it for inclusion into the upstream kernel. For a recent example, see Bcache http://bcache.evilpiepirate.org/ http://bcache.evilpiepirate.org/, which was developed out of tree for several years before being merged a few months ago. > Please don't say things so scary without looking into it. Why do you find this scary? And why do you think that I didn't look into this?
- microcolonel 13y ago
  Ahh, the way you said it made it sound like the first bit was you talking out your ass, assuming that they hadn't merged any of their work by a few pages on their site. I am currently on a very restricted link, so I was not able to check the commit logs.