From: Andi Kleen <ak@muc.de>
To: Jan Vicherek <honza@ied.com>
Cc: Marc Lehmann <pcg@goof.com>, linux-kernel@vger.rutgers.edu
Subject: Re: clarification : Re: "renice" netowork usage.
Date: 10 May 1998 03:22:43 +0200 [thread overview]
Message-ID: <k21zu22a3g.fsf@zero.aec.at> (raw)
In-Reply-To: Jan Vicherek's message of Sat, 9 May 1998 22:08:10 -0400 (EDT)
Jan Vicherek <honza@ied.com> writes:
>
> My understanding of TCP tells me that "if the line conditions are
> poor", the server adjusts the TCP window size to something smaller. Now
> how the heck would the server knows what kind of line conditions are
> ahead?! It doesn't. So how can it adjust the window side then ? By
> guessing the line conditions from number and latency of ACKs.
Read up on http://ftp.ee.lbl.gov/floyd/cbq.html, and maybe
http://ftp.ee.lbl.gov/floyd/ecn.html too. Linux implements the first
already, but there is no documentation (yet) and the code is still
rather experimential and rough. Note that the best way to implement
that is not on the end host, but rather on the router before the
bottleneck link.
If you want a basic explanation of the current TCP congestion
avoidance algorithms read RFC 2001. The current algorithm penalizes
slow streams over fast streams a bit though.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
prev parent reply other threads:[~1998-05-10 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980509215645.47060@cerebro.laendle>
1998-05-10 2:08 ` clarification : Re: "renice" netowork usage Jan Vicherek
1998-05-10 1:22 ` Andi Kleen [this message]
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=k21zu22a3g.fsf@zero.aec.at \
--to=ak@muc.de \
--cc=honza@ied.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=pcg@goof.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