public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Allan Sandfeld Jensen <snowwolf@one2one-networks.com>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bandwidth 'depredation' revisited
Date: Tue, 11 Jun 2002 22:59:19 +0200	[thread overview]
Message-ID: <200206112259.19131.snowwolf@one2one-networks.com> (raw)
In-Reply-To: <3D05EEAF.mailZE11URHZ@viadomus.com> <3D060FF6.5000409@fugmann.dhs.org>

On Tuesday 11 June 2002 16:57, Anders Fugmann wrote:
> When you start a big download, you actually request a server to send as
> much data as possible to you. Quickly, the packet queues on your ISP's
> side gets filled up. If these queues are big (can hold many packets) you
> will see a rather high latency when trying to retrieve replys, since any
> pakcets (incl. ACK) will need first to enter the queue, and wait for
> their turn to be send to you.
>
> The best solution would be to install some sort of traffic shaping on
> the remove side (you ISP), but that is often(/always) not a possible
> solution.
>
> The second best solution is to simple drop packets comming in too 
> quickly from the interface. By this, the sending machine will slow down 
> transmission. The idea is to keep the queues at you ISP empty.

You could also just delay trafic from certain IPs. Or even better, you could 
postpone acknowledgedments until you get the right distribution.

I know routers that do the former to gain fair download on shared internet 
connections, but the second would be a lot nicer.

  parent reply	other threads:[~2002-06-11 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 12:35 Bandwidth 'depredation' revisited DervishD
2002-06-11 14:57 ` Anders Fugmann
2002-06-11 17:18   ` DervishD
2002-06-11 18:25     ` Anders Peter Fugmann
2002-06-11 20:20   ` Marius Gedminas
2002-06-11 20:59   ` Allan Sandfeld Jensen [this message]
2002-06-14  3:35   ` Albert D. Cahalan
2002-06-14  9:16     ` Anders Peter Fugmann
2002-06-14  9:17   ` lkml

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=200206112259.19131.snowwolf@one2one-networks.com \
    --to=snowwolf@one2one-networks.com \
    --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