From: Daniele Lacamera <netdev@danielinux.net>
To: "Xiaoliang (David) Wei" <davidwei79@gmail.com>,
Giovanni Pau <gpau@cs.ucla.edu>,
Carlo Caini <ccaini@deis.unibo.it>,
Rosario Firrincieli <rfirrincieli@arces.unibo.it>
Cc: netdev <netdev@vger.kernel.org>
Subject: [ANNOUNCE] FYI: MultiTCP for linux-2.6.19
Date: Fri, 19 Jan 2007 13:15:06 +0100 [thread overview]
Message-ID: <1169208906.2266.44.camel@inspiron> (raw)
MultiTCP[1] is (yet another) Linux TCP patch intended for
researchers/developers, which can report TCP events in the kernel logs
in order to watch TCP internal variables.
Furthermore, it includes TCP Pacing and Hoe's initial ssthresh
estimation[2]. Their use in satellite links is strongly recommended by
the TCP-Hybla authors in order to mitigate congestion episodes and limit
the initial cwnd overshoot phenomenon respectively.
A new version for linux-2.6.19 has been released at
http://www.sf.net/projects/multitcp/
Hybla's authors future goal would be to produce official patches for
both Pacing and initial ssthresh estimation, by freeing the latter one
implementation from the TCP kernel logs engine and getting the current
tcp_sock structure slimmer.
Meanwhile, we will appreciate if the comparative tests made on Linux
congestion control will include the two algorithms described above when
using TCP-Hybla.
[1]
C. Caini, R. Firrincieli and D. Lacamera, "A Linux Based Multi TCP
Implementation for Experimental Evaluation of TCP Enhancements", SPECTS
2005, Philadelphia, July 2005.
C. Caini, R. Firrincieli, D. Lacamera, "An emulation approach for the
evaluation of enhanced transport protocols performance in satellite
networks", IEEE Globecom 2006 - Satellite and Space Communications, 27
November-1 December 2006, San Francisco, CA, USA.
[2]
J. C. Hoe, "Improving the Start-up Behavior of a Congestion Control
Scheme for TCP", ACM SIGCOMM 1996, pp. 270-280
Regards,
--
Daniele Lacamera
reply other threads:[~2007-01-19 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1169208906.2266.44.camel@inspiron \
--to=netdev@danielinux.net \
--cc=ccaini@deis.unibo.it \
--cc=davidwei79@gmail.com \
--cc=gpau@cs.ucla.edu \
--cc=netdev@vger.kernel.org \
--cc=rfirrincieli@arces.unibo.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox