> The qdisc wrr. It has the possibility to set "penalty" through different
> weigths.
Then you can't. A qdisc can only have 1 parent.
> > If you want to improve latency for certain traffic, you can create 2 htb
> > classes. One with a lower prio parameter to get low latency and an other
> > class with all other traffic.
> > To give each pc on the network the same opportunity to send something,
> > create 100 sub classes with parent=second class. To get fairness / pc,
> > you can add a sfq to each class. You can do the same for the low prio
> > class. If you don't care about fairness / pc, you can add 1 esfq qdisc
> > instead of the 100 sub classes.
>
> I want to make sure that given an assortment of packets containing
> different kinds of traffic, say game and download, the game packets will
> be in front of the download packets when they are dequeued from the
> leafs of the wrr qdisc.
>
> The idea was to have all traffic go through the same wrr qdisc. They
> just had to "reordered" before going to the wrr qdisc. Does that make
> sense?
Not really. Imagine you have a ssh packet so it's placed in the low delay
class. But after that, it's placed in the same class (under the wrr qdisc)
with all the other packets, so it has to wait. Bye, bye low delay.
> This solution could very well give better performance for the filtered,
> interactive traffic. I just have to make sure that the volume i HS
> doesn't get to big to keep users happy.
I don't know if this setup is going to work. I never tried something like
that, but in theory it should work. I'm just curious if you will get low
delays for the HS class.
> They're so picky ;-)
I'm sure you can find a solution so you can keep your users happy :)
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
