LAlambda·Sep 20, 2013
When they say that, they mean in their fork of the Linux kernel: https://github.com/multipath-tcp/mptcp not in the official upstream kernel from Linus 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 t
Read the rest
he "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/, 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?