From: Angelo Dell'Aera <buffer@antifork.org>
To: Linux-Net <linux-net@vger.kernel.org>
Cc: Netdev <netdev@oss.sgi.com>
Subject: TCP congestion control article
Date: Fri, 25 Jun 2004 12:39:53 +0200 [thread overview]
Message-ID: <20040625123953.1d42b556.buffer@antifork.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I just want to point out to you a really interesting article published
by two members of my research group. The paper is entitled
"Performance Evaluation and Comparison of Westwood+, New Reno and
Vegas TCP Congestion Control" and it aims at evaluating these three
algorithms in really different scenarios.
You may find it at
http://buffer.antifork.org/westwood/ccr_v31.pdf
Best regards.
- --
Angelo Dell'Aera 'buffer'
Antifork Research, Inc. http://buffer.antifork.org
PGP information in e-mail header
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA3AD5pONIzxnBXKIRArSJAJ9AZoybNpTpLxj2XPZ3IBm/zfgfzwCguu3m
+XKmZTP/fvy73EM5MHOUY6g=
=0DyV
-----END PGP SIGNATURE-----
next reply other threads:[~2004-06-25 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 10:39 Angelo Dell'Aera [this message]
2004-06-25 16:11 ` TCP congestion control article David S. Miller
2004-06-29 18:34 ` Angelo Dell'Aera
2004-06-29 19:44 ` David S. Miller
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=20040625123953.1d42b556.buffer@antifork.org \
--to=buffer@antifork.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).