netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: John Heffner <jheffner@psc.edu>, Andi Kleen <ak@suse.de>,
	linux-net <linux-net@vger.kernel.org>,
	netdev@oss.sgi.com
Subject: Re: [RFC] TCP Vegas for 2.6
Date: Tue, 09 Mar 2004 10:56:52 -0800	[thread overview]
Message-ID: <404E1374.5050600@us.ibm.com> (raw)
In-Reply-To: <20040309102206.33c1720c@dell_ss3.pdx.osdl.net>

Stephen Hemminger wrote:

> Every case I tested has vegas faster than the default reno.  It is especially
> noticeable over the DSL.  The current implementation is not ready to be turned
> on by default though.

Stephen, just a question regarding your testing.
(To save me some effort ;-)). What tests did you
run, which testcases, and if it wasn't some standard
benchmark, will you consider inclusion of those tests into
the LTP or equivalent?

[Strange words like "leverage" and "synergy" are popping
  into my head but I'm suppressing them ;)]

thanks,
Nivedita



  reply	other threads:[~2004-03-09 18:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 21:04 [RFC] TCP Vegas for 2.6 Stephen Hemminger
2004-03-08 21:21 ` Andi Kleen
2004-03-08 21:30   ` Stephen Hemminger
2004-03-08 21:36     ` Andi Kleen
2004-03-08 21:45       ` Stephen Hemminger
2004-03-08 23:37         ` David S. Miller
2004-03-09 17:52         ` John Heffner
2004-03-09 18:03           ` Andi Kleen
2004-03-09 18:11             ` John Heffner
2004-03-09 18:22               ` Stephen Hemminger
2004-03-09 18:56                 ` Nivedita Singhvi [this message]
2004-03-09 19:03                   ` Stephen Hemminger
2004-03-09 19:36                     ` Nivedita Singhvi
2004-03-09 18:58                 ` jamal
2004-03-08 21:51       ` Nivedita Singhvi
2004-03-08 23:31       ` 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=404E1374.5050600@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=ak@suse.de \
    --cc=jheffner@psc.edu \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    /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).