From: "David S. Miller" <davem@redhat.com>
To: "Angelo Dell'Aera" <buffer@antifork.org>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP congestion control article
Date: Fri, 25 Jun 2004 09:11:58 -0700 [thread overview]
Message-ID: <20040625091158.2e84ed3a.davem@redhat.com> (raw)
In-Reply-To: <20040625123953.1d42b556.buffer@antifork.org>
On Fri, 25 Jun 2004 12:39:53 +0200
"Angelo Dell'Aera" <buffer@antifork.org> wrote:
> 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.
Would be interesting to compare with BITCP which we have enabled
by default now in current 2.6.x kernels.
next prev parent reply other threads:[~2004-06-25 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 10:39 TCP congestion control article Angelo Dell'Aera
2004-06-25 16:11 ` David S. Miller [this message]
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=20040625091158.2e84ed3a.davem@redhat.com \
--to=davem@redhat.com \
--cc=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).