[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Traffic Control: 'bounded' and 'isolated' keyword problems.

On Wed, 30 Aug 2000, Jonathan Earle wrote:

> Hi,
> I'm still plugging away with TC, trying to get it to do what I want.  What I
> want to do is illustrated in the diagram below.  I have a cbq qdisc, which
> has its bandwidth defined as 3.3mbit.  Inside I define three cbq classes,
> each with a rate of 1.1mbit.  They are defined as bounded (so they should
> only tolerate a maximum of 1.1mbit), and isolated (so they won't loan their
> BW to any other classes).  Each of these classes has a subclass of type cbq,
> and a rate of 1mbit.  The script I use ('ep') to set up the filtering is
> at around 7mbit (combined), the streams are each limited to the total
> bandwidth of the pipe, in this case, around 3.3mbit.  I would have figured
> the bounded and isolated keywords specified would have limited the egress
> rate to a 2.2mbit combined maximum (two flows @ 1.1mbit each).  If I put the
> isolated keyword on the subclasses, then it acts as though there is no rate
> limiting at all - the egress rate is the same as the ingress rate - around
> 7mbit.  I've tried with just the 1:1, 1:2 level classes, and I can't limit
> the amount or location of where they are able to borrow BW from with use of
> just the bounded and isolated keywords.

You dont say what happens when you remove the 'isolated' operator.

> Any thoughts as to where I went wrong?

I dont think you need the isolated parameter.