netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Cheng Jin <chengjin@cs.caltech.edu>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: Long-term TCP connections suffer on high-latency links.
Date: Thu, 29 Jul 2004 23:25:36 -0700	[thread overview]
Message-ID: <4109E9E0.9010208@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407292206490.9625-100000@fast2.cs.caltech.edu>

Cheng Jin wrote:

> As of 2.6.6 kernel, TCP Westwood, which mainly addresses issues in 
> wireless networks, BIC TCP, and TCP Vegas are all included besides TCP 
> NewReno, although not enabled by default.  The others can be downloaded 
> from the given websites.  There are probably others that I forgot to 
> mention.  Apologies to them in advance.

Any chance Westwood will get into the 2.4 kernel as well?

> Making the current TCP more ``efficient'' by increasing cwnd faster is not 
> an adequate solution, although doing that will likely produce higher 
> throughput in today's Internet.  We also must consider issues such as 
> fairness to other flows, stability of the network in terms of queue
> oscillation and packet loss, and how well these solutions would scale in 
> future networks.  A lot of experiments are still needed to determine which 
> is the most appropriate under what circumstances.

Both of the two that I read about (Highspeed TCP and FAST tcp)
did indeed increase the cwnd faster, unless I mis-understood
the papers.  Granted they do it in clever ways...

Thanks for the links.

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2004-07-30  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30  5:01 Long-term TCP connections suffer on high-latency links Ben Greear
2004-07-30  5:28 ` Cheng Jin
2004-07-30  6:25   ` Ben Greear [this message]
2004-07-30  7:34     ` Baruch Even
2004-07-30 16:16     ` Stephen Hemminger

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=4109E9E0.9010208@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=chengjin@cs.caltech.edu \
    --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).