Differences between current version and predecessor to the previous major change of DCCP.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 53 | Last edited on Wednesday, May 30, 2007 4:09:28 pm | by IanMcDonald | |
| Older page: | version 51 | Last edited on Wednesday, December 13, 2006 10:29:45 am | by IanMcDonald | Revert |
@@ -12,13 +12,13 @@
!!DCCP stack for Linux
Much of this page is shifting to http://linux-net.osdl.org/index.php/DCCP - that page is considered the definitive reference for the DCCP implementation for Linux.
-DCCP is present in the [LinuxKernel]. This is being maintained by ArnaldoMelo at present. The history of this is that it draws from the code of Patrick ~McManus, Lulea and the [WAND] group
that IanMcDonald is part of. It was accepted into the LinuxKernel by LinusTorvalds in 2.6.14. It continues to evolve rapidly at time of writing (preparatory 2.6.20) and it usually pays to get the latest code from a [Git] tree.
+DCCP is present in the [LinuxKernel]. This is being maintained by ArnaldoMelo at present. The history of this is that it draws from the code of Patrick ~McManus, Lulea and the WandGroup
that IanMcDonald is part of. It was accepted into the LinuxKernel by LinusTorvalds in 2.6.14. It continues to evolve rapidly at time of writing (preparatory 2.6.20) and it usually pays to get the latest code from a [Git] tree.
The core DCCP stack was written by ArnaldoMelo using the Linux [TCP] implementation as a model, with DCCP being used as a way to identify code in the [TCP] implementation that could be made generic and shared with other INET transport level implementations. This resulted in the generalisation of code related to the minisockets representing both TCP_SYN_RECV/DCCP_RESPOND and TCP_TIME_WAIT/DCCP_TIME_WAIT status, code related to established/timewait/listen sockets (inet_lookup, inet_lookup_established, etc), the interface to get sock information (tcp_diag), and many other functions and data structures, with more expected to be generalised and eventually used by [SCTP] and any other INET transport protocols that may be introduced in the future.
-The [CCID]3 code was, as IanMcDonald mentioned, drawn from the [WAND] group
, that in turn got it initially from the Lulea [FreeBSD] codebase and made it work in the core DCCP stack written by Patrick ~McManus. It was modified by ArnaldoMelo to fit Linux standards wrt list handling and several other aspects.
+The [CCID]3 code was, as IanMcDonald mentioned, drawn from the WandGroup
, that in turn got it initially from the Lulea [FreeBSD] codebase and made it work in the core DCCP stack written by Patrick ~McManus. It was modified by ArnaldoMelo to fit Linux standards wrt list handling and several other aspects.
The [CCID] modular infrastructure was written to fit the [CCID]3 existing interface, but will probably be changed in the near future in the effort to have a generic CA (Congestion Avoidance) infrastructure shared with [TCP] (and others, who knows), continuing work on the existing [TCP] CA infrastructure put in place by Stephen Hemminger.
To have a look at the theoretical performance of [CCID]3 see http://wand.net.nz/~perry/max_download.php - the codebase currently calculates s using a weighted average.
