All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander thrill12@gmx.net
To: lartc@vger.kernel.org
Subject: [LARTC] Limiting Outgoing and Incoming Bandwidth in Linux
Date: Tue, 05 Dec 2000 19:21:07 +0000	[thread overview]
Message-ID: <marc-lartc-98373938217002@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938217000@msgid-missing>

<PRE>At 18:39 5-12-00 +0200, you wrote:
&gt;<i>what about using ingress policeing instead of rshaper for limiting incomming
</I>&gt;<i>bandwidth?
</I>And does anyone have some information on how exactly the CBQ-routine 
distributes the bandwidth fairly among several channels that may borrow 
from each other, as in for example:

* 3 upload channels of 32 kbit, non-bounded
* one person starts to upload, borrowing from the other channels totalling 
to 96 Kbit
* then another person comes in, who only gets 32 kbit while the first 
uploader still holds 64 kbit for upload -&gt; this is not exactly what I call
'fair' queueing, is it possible to prevent this behaviour?

Sander



</PRE>

      parent reply	other threads:[~2000-12-05 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05 15:39 [LARTC] Limiting Outgoing and Incoming Bandwidth in Linux 2.2 Brian
2000-12-05 16:39 ` Dimitar
2000-12-05 19:21 ` Sander [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=marc-lartc-98373938217002@msgid-missing \
    --to=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.