From: Simon Lodal <simonl@parknet.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Large number of HTB classes
Date: Fri, 27 Aug 2004 10:22:13 +0000 [thread overview]
Message-ID: <412F0B55.5040101@parknet.dk> (raw)
In-Reply-To: <412EF503.4010908@parknet.dk>
HFSC seems interesting, but does it really work well? I am not afraid of
new stuff, but bleeding edge is probably too risky.
That HTB problem, I guess you mean it is possible to have available
bandwidth, but when some of it has been distributed between users, all
users' ceils go below their quantums?
But that implies that users have low ceils? Wouldn't it be solved by
setting all users' ceil to the full link bandwidth?
The doubly linked list patch you mention, I believe it should be in
vanilla kernel since 2.4.20-22 or something? I use 2.4.27 here. If not,
do you have a link for it?
Simon
Tomasz Paszkowski skrev:
> On Fri, Aug 27, 2004 at 10:46:59AM +0200, Simon Lodal wrote:
>
>>I am planning a setup with thousands of classes in a HTB qdisc, say from
>>1:1000 to 1:2000, each with a very small rate and a big ceil, for fair
>>sharing of a 45mbit link.
>
>
> Consider using HFSC. HTB is not the best solution for such a number of classes
> with small rate. Users will not be able to get the whole ceil even if
> there will be avaliable bandwidth.
>
> Secondly make sure your're using kernel with double linked list patch applied
> to qdisc api.
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-27 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 8:46 [LARTC] Large number of HTB classes Simon Lodal
2004-08-27 9:11 ` Tomasz Paszkowski
2004-08-27 9:16 ` Rio Martin.
2004-08-27 10:22 ` Simon Lodal [this message]
2004-08-27 11:40 ` Tomasz Paszkowski
2004-08-27 13:53 ` Simon Lodal
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=412F0B55.5040101@parknet.dk \
--to=simonl@parknet.dk \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox