From: Wingtung.Leung s965817@uia.ua.ac.be
To: lartc@vger.kernel.org
Subject: [LARTC] Limiting Outgoing and Incoming Bandwidth in Linux 2.2
Date: Thu, 07 Dec 2000 00:00:09 +0000 [thread overview]
Message-ID: <marc-lartc-98373938217010@msgid-missing> (raw)
<PRE>On Tue, 5 Dec 2000, Sander wrote:
><i> And does anyone have some information on how exactly the CBQ-routine
</I>><i> distributes the bandwidth fairly among several channels that may borrow
</I>><i> from each other, as in for example:
</I>><i>
</I>><i> * 3 upload channels of 32 kbit, non-bounded
</I>><i> * one person starts to upload, borrowing from the other channels totalling
</I>><i> to 96 Kbit
</I>><i> * then another person comes in, who only gets 32 kbit while the first
</I>><i> uploader still holds 64 kbit for upload -> this is not exactly what I call
</I>><i> 'fair' queueing, is it possible to prevent this behaviour?
</I>
We have tried the SFQ with seperate subclasses and I believe it worked
well. Can you give your setup (classes and qdiscs) in tc commands?
</PRE>
next reply other threads:[~2000-12-07 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 0:00 Wingtung.Leung [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-05 15:39 [LARTC] Limiting Outgoing and Incoming Bandwidth in Linux 2.2 Brian
2000-12-05 16:39 ` Dimitar
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-98373938217010@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.