-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
Linux Kernel MultiPath TCP | ||
========================== | ||
:type: Lightning Talk | ||
:conference: FOSDEM 2012 | ||
:presenter: Christoph Paasch | ||
:presented: 4/2/2012 | ||
:url: http://mptcp.info.ucl.ac.be | ||
|
||
TCP identifies connection by the 5-pule and as part of it is IP which is | ||
connected to the interface. Idea is to use all interfaces. New standard is | ||
called MTCP. | ||
|
||
MPTCP was developed by university. | ||
|
||
We start with standard socket IP. Applications use that to comunicate to | ||
Multipath TCP without knowing it. Multipath creates TCP subflow. It will start | ||
with master subsocket and determine whether other server is capable of | ||
multipath and if they are, it will create another TCP subflows. This way | ||
existing firewalls are capable of using it. | ||
|
||
Multipath keeps queue for send data and sheduler is sending them through | ||
subflows. On the other part there are queue for each interface but also general | ||
merging queue. With two same lines, for large data speed is doubled, for | ||
smaller requests overhead is to much. |