public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diwaker Gupta <diwaker@cs.ucsd.edu>
To: linux-kernel@vger.kernel.org
Subject: Linux TCP implementation
Date: Mon, 16 Feb 2004 16:40:48 -0800	[thread overview]
Message-ID: <40316310.9080805@cs.ucsd.edu> (raw)

Maybe this question has already been burnt to death, but I wasn't able 
to find an answer on the archives or on the FAQ. So here goes:

I was just reading about the various TCP implementation -- Reno, Tahoe 
and Vegas in particular -- and I was wondering about the TCP 
implementation in Linux. AFAIK (and from looking at the source code), it 
seems current kernels are using a tweaked version of Reno. I'm also 
aware that at some point of time (2.1.x?) Vegas was introduced into the 
mainstream kernels, but then withdrawn.

I want to gather the LKML readers' thoughts on this -- to me it seems 
that TCP Vegas in superior to Reno in almost all ways, and will really 
help to bring down network congestion substantially if a large number of 
senders begin to use it (read "if introduced in the mainstream kernel"). 
The question then is, why is TCP Vegas not here yet? And are there any 
plans to incorporate it in the future?

-- 
Diwaker Gupta
Graduate Student, Computer Sc. and Engg.
University of California, San Diego
<http://www.cs.ucsd.edu/~dgupta>

             reply	other threads:[~2004-02-17  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  0:40 Diwaker Gupta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-18 19:12 Linux TCP implementation Maciej Soltysiak
2004-02-18 22:45 ` Stephen Hemminger
2004-03-22 20:58 m k
2004-03-23  2:28 ` 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=40316310.9080805@cs.ucsd.edu \
    --to=diwaker@cs.ucsd.edu \
    --cc=diwaker@ucsd.edu \
    --cc=linux-kernel@vger.kernel.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